Beta 5 and its lockfile

[jbrowne]

Marcus

   Thanks for the input. I Did a bit more digging. I finally tried to run lock 
by itself on a test file, It still had the segmentation fault. My guess is 
that this is a library version problem.

   I'm running SuSE 6.1 Linux on a twin P2 400 SMP. With beta 4 it had only 
one problem starting a monitor, but a patch was posted on the defunct forum. 
Now lock is trying to access memory it shouldn't. I tried to hack the startup 
script to run without the lockout, but it crashed after the first menu anyway.

   Oh well, try, try again. I THEN downloaded beta 6 source and tried to 
compile that. After several warnings of duplicate naming - it died at 
"undefined reference to __waddbytes". I'll post more on that thread.

   Well, there went a 4 day weekend that I was going to devote to 
photoanalysis and some coding.

   So I removed the files for about the 20TH time and reinstalled beta 4. It 
works! If the code did not change, something about the compile must have.

  This is a very abbreviated version of my various attempts.

  I'm planning to pick up SuSE 6.3 in the hope that it helps. I also have Red 
Hat, but haven't loaded GRASS on that machine yet. With luck, I'll have some 
others running soon.At this pace of change, Debian and its getupdate command 
is getting to look very attractive.

   AAAaahhhhh....  life at the bleeding edge, isn't it wonderful!

   Thanks again
                                    Jim


>===== Original Message From Markus Neteler <neteler at geog.uni-hannover.de> 
=====
>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 :-)
>
>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