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 TMPDIR to be /tmp/$LOGNAME
> better than
> Fix the web browser to download things into $HOME/Downloads
> by default (instead ot dumping things directly into $TMPDIR)
I am not sure whether it is usefull to try that since this behavoiur is
too common in applications. We could try to fight but the windmills are
likely going to win (unless we fight with Leopard-2 tanks etc. ... :-) )
...
> If I'm downloading something valuable, I'm going to need to copy it out of
> TMPDIR anyways, and any cost of doing the initial write()s to $HOME instead
> of $TMPDIR pales next to the cost of having to invoke "cp $TMPDIR/foo $HOME".
> And, if I'm not going to keep it, as long as the browser cleans up after
> itself, I shouldn't care what happens behind the scenes
But that's what many users do in this case: They view something in xpdf
or acroread and if they "like" it they copy the files from it's
temporary location to a permenent in ${HOME}. That's pretty much
unavoidable...
> Unless you are seriously implying that (potential) NFS access to $HOME
> is the performance bottleneck in downloading and viewing a PDF file from
> the web? If so, it sounds like the admin has bigger problems to solve
> than simple modifications to TMPDIR can solve.
... the part where I would be worried are name collisions when working
in the same account from multiple machines...
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.mainz at nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
