Re: ORBit-like /tmp functions

[Frederic Crozat <fcrozat mandrakesoft com>]

Le sam 14/08/2004 à 01:33, Havoc Pennington a écrit :
> On Fri, 2004-08-13 at 11:57, Frederic Crozat wrote:
> > Le jeu 05/08/2004 à 09:48, Havoc Pennington a écrit :
> > > 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...

Well, using /var/tmp could lead to lock an entire system if quota are
not enabled on the system by filling disk space. By forcing tmp in
$HOME, at least, you know users won't be able to screw system partitions
and then the entire system..

-- 
Frederic Crozat <fcrozat mandrakesoft com>
Mandrakesoft