GRASS lock problem

[Markus Neteler]

> >/usr/local/grass42/etc/GIS.sh: /usr/local/grass42/etc/lock: No such file
> >  or directory
> >Unable to properly access /home/hamannj/.gislock
> >Please notify system personel.
> >[hamannj at ren hamannj]$ =
> >I installed the grass binaries exactly as instructed from the web site and
> >still get this problem. =
 
> Several of us are getting that exact error message ( with our own machine n=
> ame,
> of course).    I don't know what to try next, but I believe Markus is 
> looking into it (see quote below).
>  > > We will find a solution!

Hi friends,

just now I have installed GRASS 4.2.1 (V.21) on a "fresh" Linux System
running SuSe6.0-Linux.
But I could not reproduce your error message. I downloaded the current
Linux binaries and strickly followed my instructions (without extra 
knowledge!). 
So we have to proceed stepwise to locate the problem. You may post 
personally to me, I will send the solution to the list then, when 
(not if) we find it:

1. Are you all running *Redhat* Linux? Which version?

2. Is there existing the file
    /usr/local/grass42/etc/lock

   Execute it, it should say
   
      /usr/local/grass42/etc > lock
      usage: lock file pid

3. Check the permissions for /usr/local/grass42/locks
   /usr/local/grass42 > ls -la locks/
   total 3
   drwxrwxrwt   4 root     root         1024 Apr 14 15:40 .
   drwxr-xr-x  13 root     root         1024 Apr 14 15:38 ..
   drwxrwxrwt   2 root     root         1024 Apr 14 15:43 ifbo22

  It should look like this (with different machine's name certainly)

BTW: Valid are the online instructions. I changed this part of 
    locks permission settings recently, so it may not be correct in 
    the instructions included in the Linux package.

4. Check the permissions of your home directory:
   cd $HOME
   akk at ifbo22:~ > ls -la .
   drwxr-xr-x  17 akk      users        2048 Apr 14 15:49 .
   drwxr-xr-x   8 root     root         1024 Feb 10 19:03 ..
   
   Here it belongs user "akk", certainly he needs write/read/execute 
   permissions (first drwx in line containing ".").

   This should be o.k.

   Test it in your home with
    touch .gislock     
    rm .gislock

   This should work.

-----------------------------
Is there any other user in the list having an idea? I haven't seen
this problem yet in my "GRASS life".

With regards

   Markus Neteler