The /tmp/grass6-<user>-<pid> directories contain per-session state
(the $GISRC file, as well as any sockets used for display monitors).
There should be one such directory created for each session. They
should be deleted when the session terminates, but they are often left
behind. Stale directories shouldn't cause any problems, unless they
are owned by someone other than the user.
Common reasons for /tmp/grass6-<user>-.. being left behind are when the
GUI startup menu is given but the user presses Cancel, or when creating
a new location from EPSG code on the startup GUI (exit & restart).
From looking at my /tmp dir I seem to accumulate them at a rate of about
On Wed, Jul 05, 2006 at 06:20:54PM +1200, Hamish wrote:
Glynn Clements <glynn@gclements.plus.com> wrote:
> The /tmp/grass6-<user>-<pid> directories contain per-session state
> (the $GISRC file, as well as any sockets used for display monitors).
>
> There should be one such directory created for each session. They
> should be deleted when the session terminates, but they are often left
> behind. Stale directories shouldn't cause any problems, unless they
> are owned by someone other than the user.
Common reasons for /tmp/grass6-<user>-.. being left behind are when the
GUI startup menu is given but the user presses Cancel,
... which should be possible to get fixed in
lib/init/gis_set.tcl
around line 592
?
or when creating
a new location from EPSG code on the startup GUI (exit & restart).