[winGRASS] Re: winGRASS and cygwin, and GIS lock issue
Jeff McKenna
jmckenna at dmsolutions.ca
Mon Dec 4 08:55:22 EST 2006
I have been quietly battling this same error, with GRASS 63 and 6.2.0,
on Cygwin, and following all discussions. I've seen people say that
it's due to a missing PostgreSQL on the machine (not true in my case),
and now this latest news (although it seems to apply only to
native-GRASS users, whereas I'm trying to use Cygwin...in any case the
locking trick doesn't work for me either).
Anyway I'll keep trying.
jeff
Isaac Ullah wrote:
> Hi Listers,
>
> Jonathan is exactly right about the issues with the new winGRASS for
> those of us that previously had CYGWIN with GRASS installed on our
> machines. Removing CYGWIN is not easy, however, as there is no
> "uninstall" option for CYGWIN. I had to search around for a solution:
> Apparently, some of the files in the Cygwin directory are given very
> different perissions from ordinary files. They are assigned "system" as
> their owner, and even if you are an administrator, you cannot delete
> them with the default way windows wants to have things organized. In a
> standard windows exploer window, you have to click tools > folder
> options, and select the "view" tab from the dialogue box that pops up.
> You have to scroll down the list, and uncheck the box next to "use
> simple file sharing". Now when you right click on an item, and select
> proerties, there are several new tabs in the window. You must go to the
> "security" tab, and change the owner ship and permissions associated
> with those cygwin files that are apparently undeleteble. Once that is
> done, you should now be able to manually delete everything asscociate
> with cygwin (which conveniently is all in the cygwin directory).
> Also, Jonathan, your solution to the Locking problem is probably
> okay. I know that it was put in there in the Linux version to prevent
> more than one user at a time from reading and writing on the same set of
> GRASS files. This was only needed if your GIS database was located on a
> server or was shared over a network. Since this does not apply to the
> curretn WinGRASS, you can actually simply delete those lines without any
> issue. In fact, that may be something that should be done to the
> WinGRASS packages anyway...
>
> Cheers,
>
> Isaac
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 2 Dec 2006 14:24:13 -0500
> From: "Jonathan Aguero" <jua130 at psu.edu <mailto:jua130 at psu.edu>>
> Subject: RE: [winGRASS] grass native installation problem
> To: "'Bryan Keith'" < bryan at geomega.com <mailto:bryan at geomega.com>>,
> "'Jack'"
> <jacques.charroy at laposte.net
> <mailto:jacques.charroy at laposte.net>>
> Cc: wingrass at grass.itc.it <mailto:wingrass at grass.itc.it>
> Message-ID:
> <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAATR1TnoRRqU2OBfkDJYrxesKAAAAQAAAAoAwKhMpEb0isJHsu0qEyhAEAAAAA at psu.edu
> <http://psu.edu>>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Brian and Jacques,
> I just had the same problem with my WinXP system. It seems that the
> problem
> was related to my old Cygwin installation. I removed cygwin and
> clean up the
> environmental variables related and then GRASS worked.
> If the CYGWIN variable is defined in your system, the grass init script
> assumes that the shell is bash instead of the bourne shell (sh) used by
> MINGW/msys.
> I hope this help you guys.
>
> Jonathan Aguero Valverde
> Research Assistant and Ph.D. Candidate
> Pennsylvania State University
> The Pennsylvania Transportation Institute
> 201 Transportation Research Building
> University Park, PA 16802
> www.personal.psu.edu/jua130 <http://www.personal.psu.edu/jua130>
>
> -----Original Message-----
> From: wingrass-bounces at grass.itc.it
> <mailto:wingrass-bounces at grass.itc.it>
> [mailto:wingrass-bounces at grass.itc.it
> <mailto:wingrass-bounces at grass.itc.it>]
> On Behalf Of Bryan Keith
> Sent: Monday, October 02, 2006 10:12 AM
> To: Jack
> Cc: wingrass at grass.itc.it <mailto:wingrass at grass.itc.it>
> Subject: Re: [winGRASS] grass native installation problem
>
> I'm having the exact same problem. Anyone know how to solve it?
>
> Bryan
>
> Jacques Charroy wrote:
> > Hi,
> >
> > I recently installed the native wingrass package on two computers. On
> > one everything went well, but on the next one gis.m never managed to
> > start, although GRASS starts alright. Upon starting gis.m I get
> an error
> > box saying the following:
> >
> > Error in startup script
> > Can't read "parts(n)": no such variable
> > while executing
> > "MapCanvas::zoom_new $mon $parts(n) $parts(s).......(more)
> > (procedure "MapCanvas::zoom_gregion" line 11)
> > invoked from within.......and so forth with 5 or six levels of
> function
> > calls until:
> > invoked from within
> > (file "C:/msys/1.0/local/grass/etc/gm/gm.tcl" line 522)
> >
> > Has someone else had the same problem? any ideas how to solve that?
> >
> > Thanks,
> >
> > Jacques Charroy
> >
> > _______________________________________________
> > winGRASS mailing list
> > winGRASS at grass.itc.it <mailto:winGRASS at grass.itc.it>
> > http://grass.itc.it/mailman/listinfo/wingrass
> >
> >
>
> _______________________________________________
> winGRASS mailing list
> winGRASS at grass.itc.it <mailto:winGRASS at grass.itc.it>
> http://grass.itc.it/mailman/listinfo/wingrass
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 2 Dec 2006 14:54:49 -0500
> From: "Jonathan Aguero" < jua130 at psu.edu <mailto:jua130 at psu.edu>>
> Subject: RE: [winGRASS] Installation problem native win version
> To: <wingrass at grass.itc.it <mailto:wingrass at grass.itc.it>>, "'Neil
> Falconer'"
> < neil.falconer at absamail.co.za
> <mailto:neil.falconer at absamail.co.za>>
> Message-ID:
> <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAATR1TnoRRqU2OBfkDJYrxesKAAAAQAAAABBW/pD+cq0OpkdSDNT/yLAEAAAAA at psu.edu
> <http://psu.edu>>
>
> Content-Type: text/plain; charset="us-ascii"
>
> I worked more in the locking problem today and found a partial solution.
>
> I commented the following lines in the /grass/etc/init.sh file:
>
> # Check for concurrent use
>
> #lockfile="$LOCATION/.gislock"
>
> #"$ETC/lock" "$lockfile" $$
>
> #case $? in
>
> # 0) ;;
>
> # 1)
>
> # echo $USER is currently running GRASS in selected mapset.
> Concurrent
> use not allowed.
>
> # rm -rf "$tmp" # remove session files from tmpdir
>
> # exit 1 ;;
>
> # *)
>
> # echo Unable to properly access "$lockfile"
>
> # echo Please notify system personel.
>
> # exit 1 ;;
>
> #esac
>
> The symbol # before the line made it a comment and the locking is not
> performed by GRASS. As mention in other mails, concurrence might not
> be a
> problem in windows.
>
> It seems like many other people experienced this problem but GRASS
> keeps
> going while in some other systems crashes, it might be a difference
> in how
> updated XP is.
>
> Note that this is a very pedestrian solution, GRASS programmers
> could come
> up with a better one but in the mean time this may get you going with
> WINGRASS.
>
>
>
> Jonathan Aguero Valverde
>
> Research Assistant and Ph.D. Candidate
>
> Pennsylvania State University
>
> The Pennsylvania Transportation Institute
>
> 201 Transportation Research Building
>
> University Park, PA 16802
>
> www.personal.psu.edu/jua130 <http://www.personal.psu.edu/jua130>
>
> -----Original Message-----
> From: wingrass-bounces at grass.itc.it
> <mailto:wingrass-bounces at grass.itc.it>
> [mailto:wingrass-bounces at grass.itc.it
> <mailto:wingrass-bounces at grass.itc.it>]
> On Behalf Of Jonathan Aguero
> Sent: Friday, October 13, 2006 8:57 AM
> To: wingrass at grass.itc.it <mailto:wingrass at grass.itc.it>
> Subject: [winGRASS] Installation problem native win version
>
>
>
> Dear listers,
>
> I downloaded and installed the new native version of winGRASS
> yesterday. The
> installation apparently was successful but when I tried to start
> GRASS after
> I selected the location and mapset it flashed the following message:
>
> Locking is not supported in Windows!
>
> and close the window.
>
> I did not install PG 8.1 since I have the 8.0 version and I wanted
> to save
> the trouble so I modify the grass.bat the see at the 8.0 folder.
> Anyway the
> problem seems more OS related than PG related. My OS is XP
> professional SP2.
>
> Thanks in advance for your help.
>
>
>
> Jonathan Aguero Valverde
>
> Research Assistant and Ph.D. Candidate
>
> Pennsylvania State University
>
> The Pennsylvania Transportation Institute
>
> 201 Transportation Research Building
>
> University Park, PA 16802
>
> www.personal.psu.edu/jua130 <http://www.personal.psu.edu/jua130>
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://grass.itc.it/pipermail/wingrass/attachments/20061202/82c698ce/attachment.html
>
> ------------------------------
>
> _______________________________________________
> winGRASS mailing list
> winGRASS at grass.itc.it <mailto:winGRASS at grass.itc.it>
> http://grass.itc.it/mailman/listinfo/wingrass
>
>
> End of winGRASS Digest, Vol 6, Issue 1
> **************************************
>
>
>
>
> --
>
> Isaac I Ullah, M.A.
>
> Archaeology PhD Student,
> ASU School of Evolution and Social Change
>
> Research Assistant,
> Mediterranean Landscape Dynamics Project
> ***************************************************
> isaac.ullah at asu.edu <mailto:isaac.ullah at asu.edu>
> ullah at archaeologist.com <mailto:ullah at archaeologist.com>
>
> http://www.public.asu.edu/~iullah
> ***************************************************
>
--
Jeff McKenna
DM Solutions Group Inc.
http://www.dmsolutions.ca
More information about the grass-windows
mailing list