Re: ORBit-like /tmp functions
- From: "Gustavo J. A. M. Carneiro" <gjc inescporto pt>
- To: Federico Mena Quintero <federico ximian com>
- Cc: GTK+ development mailing list <gtk-devel-list gnome org>, Frederic Crozat <fcrozat mandrakesoft com>, GNOME Desktop <desktop-devel-list gnome org>
- Subject: Re: ORBit-like /tmp functions
- Date: Tue, 03 Aug 2004 23:41:00 +0100
A Ter, 2004-08-03 às 20:43, Federico Mena Quintero escreveu:
> 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
> readable?
>
> 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?
I don't know why orbit uses /tmp, but I can only guess that it's
because ~/ may be NFS-mounted, thus shared between multiple hosts.
Also, being NFS-mounted has other disadvantages, like less stable
locking, and increased access time. /tmp (or $TMPDIR) is much better
than ~/.
>
> Federico
>
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list
--
Gustavo J. A. M. Carneiro
<gjc inescporto pt> <gustavo users sourceforge net>
The universe is always one step beyond logic
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]