GRASS 4.2.1 lock file problem
derick at together.net
derick at together.net
Tue Apr 13 08:58:42 EDT 1999
I too still have a "lock:" problem.
When I try to start GRASS 4.2 on a SPARC Classic running Red Hat 5.2 I get
the following error
message:
bash$ grass4.2
/data/grass42/etc/GIS.sh: /data/grass42/etc/lock: cannot execute binary file
Unable to properly access /home/dan/.gislock
Please notify system personel.
bash$
I've checked the file permissions on my home directory and the ../etc
directory...they seem to be in order.
bash$ pwd
/home
bash$ ls -alt
total 3
drwx------ 9 dan dan 1024 Apr 12 19:51 dan
drwxr-xr-x 18 root root 1024 Apr 12 11:35 ..
drwxr-xr-x 3 root root 1024 Apr 5 21:47 .
bash$
bash$ pwd
/data/grass42/etc
bash$ ls -alt lock
-rwxr-xr-x 1 root root 3576 Sep 22 1998 lock
bash$
I've also installed the elfcurses libs and still no luck.
Is there a work around? Does any one know if this is a SPARC implementation
problem?
Thanks,
Dan
"Jeff D. Hamann" wrote:
> I still get the same messages.
>
> Jeff.
>
> ----- Original Message -----
> From: Markus Neteler <neteler at geog.uni-hannover.de>
> To: <grass at cecer.army.mil>
> Sent: Monday, April 12, 1999 9:01 AM
> Subject: Re: GRASS 4.2.1 lock file problem
>
> > > From: Charles Dingman <cdingman at his.com>
> >
> > > "/usr/local/grass42/etc/GIS.sh: /usr/local/grass42/etc/lock: No such
> > > file or directory
> > > Unable to properly access /home/cdingman/.gislock
> > > Please notify system personel."
> > >
> > >
> >
> > Hi,
> >
> > sorry for this problem! Please try the following:
> >
> > Create locks-directory (the directory must have the name
> > of your machine). If you don't know it name, type:
> >
> > uname -n
> >
> > The first word is the machine's name. Example:
> > hgeo02.geog.uni-hannover.de -> hgeo02
> >
> > Proceed with:
> >
> > cd locks
> > mkdir "machine_name" (the machine must have a name, not
> "localhost")
> > cd ..
> > chmod -R 1777 locks
> >
> > Example:
> >
> > cd locks
> > mkdir hgeo02
> > cd ..
> > chmod -R 1777 locks
> >
> >
> > Note, that the command order was changed in opposite to the
> > installation manual. If this helps or not, please let me know.
> > We will find a solution!
> >
> > With regards
> >
> > Markus Neteler
More information about the grass-user
mailing list