Re: ORBit-like /tmp functions
- From: Havoc Pennington <hp redhat com>
- To: Frederic Crozat <fcrozat mandrakesoft com>
- Cc: GTK+ development mailing list <gtk-devel-list gnome org>, GNOME Desktop <desktop-devel-list gnome org>
- Subject: Re: ORBit-like /tmp functions
- Date: Fri, 13 Aug 2004 19:33:38 -0400
On Fri, 2004-08-13 at 11:57, Frederic Crozat wrote:
> Le jeu 05/08/2004 �9:48, Havoc Pennington a �it :
> > On Wed, 2004-08-04 at 03:28, Frederic Crozat wrote:
> > >
> > > Well, for Mdk, I've been forced to move TMPDIR for gconf from $HOME/tmp
> > > (ie $TMPDIR) to /tmp otherwise gconf was failing for users with home on
> > > NFS with multiple logins (it is a known problem, IIRC).
> >
> > Yes it's a known problem, that's why upstream gconf already uses /tmp
> > ;-) (and in previous releases had an env variable GCONF_LOCAL_LOCKS=1 to
> > force use of /tmp)
>
> I've just checked code again and it is wrong : it is using g_get_tmp_dir
> which is reading TMP or TMPDIR variable, which is often set to
> $HOME/tmp, so you end up with locks on NFS :((
Oh, I read your message incorrectly. I thought you were talking about
homedir vs. /tmp, not TMPDIR vs. /tmp literal.
I don't think TMPDIR=$HOME/tmp is right at all - $HOME should be for
user data... if you wanted a per-user tmp I would suggest a
/var/tmp/username type of feature...
Havoc
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]