On 4/30/07, Darren J Moffat wrote:
> On a system with more than one user who uses GNOME you will actually
> reduce the number of directories in /tmp if $TMPDIR is /tmp/$LOGNAME
> rather than increase them.
Not so; I use GNOME and it doesn't leave anything in /tmp. There's
the normal .X11-{pipe,un
On 30/04/07, Bart Smaalders wrote:
> Peter Tribble wrote:
> > On 4/30/07, Darren J Moffat wrote:
> >> On a system with more than one user who uses GNOME you will actually
> >> reduce the number of directories in /tmp if $TMPDIR is /tmp/$LOGNAME
> >> rather than increase them.
> >
> > Not so; I us
On 4/30/07, John Plocher wrote:
> Paul Jakma wrote:
> >> Or, in other words, maybe the real fix here is to fix Mozilla (etc) to
> >> default their download dirs to $HOME/Downloads :-)
> >
> > /tmp/$LOGNAME/ would have my vote over anything under $HOME.
>
>
> Seriously, why is
> change TMPD
Peter Tribble wrote:
> On 4/30/07, Darren J Moffat wrote:
>> On a system with more than one user who uses GNOME you will actually
>> reduce the number of directories in /tmp if $TMPDIR is /tmp/$LOGNAME
>> rather than increase them.
>
> Not so; I use GNOME and it doesn't leave anything in /tmp. Th
James Carlson wrote:
> John Plocher writes:
>> This leads me to ask why not set TMPDIR to $HOME/tmp?
>
> I understand the impulse, but please don't do that. $HOME is commonly
> NFS-mounted, and puting $TMPDIR there will trash setuid applications.
$HOME/tmp also introduces locking issues if the s
On Sun, 29 Apr 2007, John Plocher wrote:
> This leads me to ask why not set TMPDIR to $HOME/tmp?
Ouch, potentially slow. I like having GNOME use relatively fast tmpfs
rather than NFS..
> On a single user system, it really doesn't matter which resources are
> used for this stuff - $HOME, /tmp,
James Carlson wrote:
> Casper.Dik at Sun.COM writes:
>> Unfortunately the use of TMPDIR is inherited across "su" and
>> then, when users assume roles, TMPDIR no longer works.
>
> That point would seem to be a show-stopper to me. Having an RBAC role
> fail to work because $TMPDIR is now set (when
Roland Mainz wrote:
>> 2) Bring this forward as a full case (or, I will derail it and get
>> it there anyway).
>> This is not an assessment of "good or bad". It simply does not
>> meet the
>> requirement of "obvious" for a fast-track (while option #1 does
>> seem obvious).
>
>
On Mon, Apr 30, 2007 at 09:03:58AM -0700, John Plocher wrote:
> Paul Jakma wrote:
> >>Or, in other words, maybe the real fix here is to fix Mozilla (etc) to
> >>default their download dirs to $HOME/Downloads :-)
> >
> >/tmp/$LOGNAME/ would have my vote over anything under $HOME.
>
>
> Seriously,
Darren J Moffat wrote:
> Roland Mainz wrote:
>
>>> 2) Bring this forward as a full case (or, I will derail it and get
>>> it there anyway).
>>> This is not an assessment of "good or bad". It simply does not
>>> meet the
>>> requirement of "obvious" for a fast-track (while option
Paul Jakma wrote:
>> Or, in other words, maybe the real fix here is to fix Mozilla (etc) to
>> default their download dirs to $HOME/Downloads :-)
>
> /tmp/$LOGNAME/ would have my vote over anything under $HOME.
Seriously, why is
change TMPDIR to be /tmp/$LOGNAME
better than
Fix
Darren J Moffat wrote:
> On a system with more than one user who uses GNOME you will actually
> reduce the number of directories in /tmp if $TMPDIR is /tmp/$LOGNAME
> rather than increase them.
Actually, you increase it, since if $TMPDIR is not set, GNOME puts
them in /var/tmp/. (Which is the
John Plocher writes:
> This leads me to ask why not set TMPDIR to $HOME/tmp?
I understand the impulse, but please don't do that. $HOME is commonly
NFS-mounted, and puting $TMPDIR there will trash setuid applications.
--
James Carlson, Solaris Networking
Sun Microsystems / 1 Networ
13 matches
Mail list logo
