• 1
Seconding that!

I also don't understand why so many applications insist on holding things in system-wide /tmp, while a $HOME/tmp would suffice...

E.g. On Fedora/RHEL I always set SCREENDIR accordingly:

# cat /etc/profile.d/screenrc.sh

SCREENDIR=$HOME/tmp
export SCREENDIR

It works flawlessly, and I don't have to worry about my stuff being visible system-wide.

system-wide /tmp is necessary for things like this

Think about if you home directory were mounted via NFS, AFS, GFS - pick shared filesystem of your choice, and you were to use screen on multiple machines. You'd have sockets that are busted, and a mighty long list in screen -ls. In *your* situation, $HOME/tmp might be appropriate, however in a large number of environments it would not be.

A little OT for this post, though :). I *do* agree with daemons moving stuff out, it's not the Right Place(TM)

  • 1
?

Log in