Re: ORBit-like /tmp functions
- From: Frederic Crozat <fcrozat mandrakesoft com>
- To: GTK+ development mailing list <gtk-devel-list gnome org>
- Cc: GNOME Desktop <desktop-devel-list gnome org>
- Subject: Re: ORBit-like /tmp functions
- Date: Wed, 04 Aug 2004 09:28:31 +0200
Le mar 03/08/2004 à 21:43, Federico Mena Quintero a écrit :
> On Thu, 2004-07-29 at 09:48 +0200, Frederic Crozat wrote:
> > Another potential problem is when /tmp is not readable (don't laugh, we
> > have this settings in paranoia mode), which can cause nice crash in
> > either GTK+ or ORBit :)
> 1. Does this setting make sense? Why would you not want /tmp to be
It is for a "paranoia" setting.. I'm not sure it make sense on a
standard system but on a highly secured system, it might (I'm not a
security expert, I just got the bug report caused by this setting). In
short, it is best to have code being able to cope with this situation.
> 2. What would happen if GConf just stored its lock and IOR file in
> ~/.gconfd/something? Is there a special reason why it uses /tmp?
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).
Frederic Crozat <fcrozat mandrakesoft com>
] [Thread Prev