Beta 5 and its lockfile

GRASS GRASS user
1

Jim,

Forwarded message:

From owner-GRASSLIST@baylor.edu Mon Jan 17 09:53 CST 2000
Message-Id: <1046411238831E79@webmail>
Date: Mon, 17 Jan 2000 10:45:37 -0500
Sender: owner-GRASSLIST@baylor.edu
Precedence: bulk
From: jbrowne <jbrowne@liu.edu>
To: GRASSLIST <GRASSLIST@baylor.edu>
Subject: Beta 5 and its lockfile
MIME-version: 1.0
Content-transfer-encoding: 7bit
X-Sender: jbrowne <jbrowne@liu.edu>
X-Mailer: WebMail (Hydra) SMTP v3.60
X-WebMail-UserID: jbrowne
X-EXP32-SerialNo: 00002866
X-Listprocessor-Version: 7.2 -- ListProcessor by CREN
Content-Type: text/plain; charset="ISO-8859-1"
Content-Length: 916

What did I do wrong?

I've had GRASS5beta4 running since October, I was hesitant to touch it but
yesterday I uninstalled it and installed beta5. When I tried to run it and
got:

   GIS.sh line 23: 1308 Segmentation Fault $ETC/lock $lockfile$$
   Unable to properly access /home/nydir/.gislock5

The directory is right and there should be no permission problems. I even
tried it from root, same thing. As a kludge, I commented out the exit;; line
in the script. GRASS then started, but exited too fast for me to read any
messages.

   I looked at the Beta4 source, and it seems that returning 0 flags a lock
and 1 is O.K.. The script seems to expect the opposite. I'm going to download
and check the new source.

   If this was a bug, and a fix was posted, my apologies. With both the forum
and the mail archive down, I couldn't check.

                             Thanks
                               Jim

FYI I got the same thing, did the same things, etc. It seems that a bit
of housekeeping is needed in upgrading versions - not so bad, if one knows
about it, but annoying otherwise.

Adios,
Chris
--
C.S. Cornuelle
School of Mathematics/MCIM, University of Minnesota
206 Church St. SE, Minneapolis, MN 55455
(612) 626-8930v, (612) 624-2333f, bob at math.umn.edu
Ferventer Vestite

2

Hi Jim, hi Chris,

what operating system you are using? I guess it is Linux. A current
version?

[...]

> I've had GRASS5beta4 running since October, I was hesitant to touch it but
> yesterday I uninstalled it and installed beta5. When I tried to run it and
> got:
>
> GIS.sh line 23: 1308 Segmentation Fault $ETC/lock $lockfile$$
> Unable to properly access /home/nydir/.gislock5
> Jim

[...]

Actually I have never seen this error (and working here at university
with several *different* Linux PCs). I need more information about
your systems.

FYI I got the same thing, did the same things, etc. It seems that a bit
of housekeeping is needed in upgrading versions - not so bad, if one knows
about it, but annoying otherwise.
Adios,
Chris

Of course this is not intended :slight_smile:

As "lock" is unchanged since September 1999
-rw-r--r-- neteler/user 105 1999-07-22 21:30 grass5.0beta/src/libes/lock/Gmakefile
-rw-r--r-- neteler/user 2867 1999-09-16 11:41 grass5.0beta/src/libes/lock/lock.c
-rw-r--r-- neteler/user 372 1999-09-16 11:41 grass5.0beta/src/libes/lock/try.c
-rw-r--r-- neteler/user 189 1999-09-16 11:41 grass5.0beta/src/libes/lock/unlock.c

it is surprising that the software behaves differently between beta4 and
beta5. Perhaps you changed your system somehow?

If you send further information, we will fix the problem! Others having
this problem as well may join the discussion (here or personally)!

Kind regards

Markus Neteler

3

Hi Jim, hi Chris,

what operating system you are using? I guess it is Linux. A current
version?

bob@khusro[~] 92) uname -a
Linux khusro 2.0.38 #39 Sun Dec 5 21:40:25 CST 1999 i686 unknown

Which is to say, moderately current. We will be up to 2.2 "soon."

[...]
> > I've had GRASS5beta4 running since October, I was hesitant to touch it but
> > yesterday I uninstalled it and installed beta5. When I tried to run it and
> > got:
> >
> > GIS.sh line 23: 1308 Segmentation Fault $ETC/lock $lockfile$$
> > Unable to properly access /home/nydir/.gislock5
> > Jim
[...]

Actually I have never seen this error (and working here at university
with several *different* Linux PCs). I need more information about
your systems.

> FYI I got the same thing, did the same things, etc. It seems that a bit
> of housekeeping is needed in upgrading versions - not so bad, if one knows
> about it, but annoying otherwise.
> Adios,
> Chris
Of course this is not intended :slight_smile:

Of course. ;^l

As "lock" is unchanged since September 1999
-rw-r--r-- neteler/user 105 1999-07-22 21:30 grass5.0beta/src/libes/lock/Gmakefile
-rw-r--r-- neteler/user 2867 1999-09-16 11:41 grass5.0beta/src/libes/lock/lock.c
-rw-r--r-- neteler/user 372 1999-09-16 11:41 grass5.0beta/src/libes/lock/try.c
-rw-r--r-- neteler/user 189 1999-09-16 11:41 grass5.0beta/src/libes/lock/unlock.c

it is surprising that the software behaves differently between beta4 and
beta5. Perhaps you changed your system somehow?

If you send further information, we will fix the problem! Others having
this problem as well may join the discussion (here or personally)!

Kind regards

Markus Neteler

The problem really seems to be with permissions. Grass has to be installed
as root, but used as <whatever>. Doing chmod on the appropriate files and
directories will IIRC fix the problem. As I said, so long as I remember
where the problem is it can be repaired easily.

All of which is far simpler than dealing with the security, access, and
philosophical issues required to handle this more thoroughly. :^)

Thanks.

Adios,
Chris
--
C.S. Cornuelle
School of Mathematics/MCIM, University of Minnesota
206 Church St. SE, Minneapolis, MN 55455
(612) 626-8930v, (612) 624-2333f, bob at math.umn.edu
Ferventer Vestite

4

Awhile back, I downloaded a binary tarball that unpacked with all kinds
of funky user/group permissions. I think I got it from baylor. Anyway,
distribution tarballs shouldn't preserve owner/group (as this one did)
and may be the source of your problem? Anyway, "chown -R root.staff
/usr/local/grass5.0beta5" should fix it (substitute appropriate
ownership for your setup).
--
+----------------------------------------------------+
| Eric G. Miller egm2@jps.net |
| GnuPG public key: http://www.jps.net/egm2/gpg.asc |
+----------------------------------------------------+