"/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!
----- Original Message -----
From: Markus Neteler <neteler@geog.uni-hannover.de>
To: <grass@cecer.army.mil>
Sent: Monday, April 12, 1999 9:01 AM
Subject: Re: GRASS 4.2.1 lock file problem
> From: Charles Dingman <cdingman@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!
"/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
Thanks. I had that mostly--locks was 0755 and cdingman was 1777.
I still get the same message after making the change you recommended.
I installed grass4.2 in linux RedHat 5.2. I try to convert a tiff file to a grass
raster map and display it. I use the commands:
r.in.tiff
d.rast
While it just displayed a white sheet on the graphic screen. I do not know which
step I did is not correct: the convertion or the raster map display. What should
I do?
By the way, how can I import raw image data into grass? The data are stored on
the disk rather than on the tape.
I installed grass4.2 in linux RedHat 5.2. I try to convert a tiff file to a grass
raster map and display it. I use the commands:
r.in.tiff
d.rast
While it just displayed a white sheet on the graphic screen. I do not know which
step I did is not correct: the convertion or the raster map display. What should
I do?
Try this sequence:
r.in.tiff
g.region rast=the_name_of_your_new_raster_layer
d.erase
d.rast the_name_of_your_new_raster_layer
By the way, how can I import raw image data into grass? The data are stored on
the disk rather than on the tape.
All of the GRASS imagery commands work just fine off of disk, as UNIX
tape drive names are just device paths also. When you are asked for the
name of your tape drive, just give the directory path and file name of
the file you wish to import.
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$
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@geog.uni-hannover.de>
To: <grass@cecer.army.mil>
Sent: Monday, April 12, 1999 9:01 AM
Subject: Re: GRASS 4.2.1 lock file problem
> > From: Charles Dingman <cdingman@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