On Wed, Jul 02, 2014 at 08:49:34AM -0500, Shawn K. Quinn wrote:
> On Tue, 2014-07-01 at 19:07 -0300, Rafael Zalamena wrote:
> > I also noted that would only happen on one machine which I had setup
> > one partition for /var/tmp and /tmp (and /tmp -> /var/tmp). After some
> > investigation I found out that the code that daily(8) uses to clean
> > /var/tmp is different from /tmp.
>
> Putting /var/tmp and /tmp together is a really bad idea. /var/tmp is
> supposed to survive a reboot, /tmp isn't.
>
> --
> Shawn K. Quinn <skqu...@rushpost.com>
>
Thank you for reminding that, I got my setup wrong and I should have
done my homework first. It seems that people from a while back also got
that wrong: the first appearence of the 'ssh-*' was back in 2000:
etc/daily 1.31:
Prune /tmp traversal at .X11-unix
Since /tmp might be a link to /var/tmp, prune at ssh-* or .X11-unix
like the find on /tmp does.
I've made a quick test and there is no problem in 'tmux-*' existing in
/var/tmp after a reboot. Running 'tmux attach' in a socket with no tmux
process controlling just spits out: 'no sessions' and if you run 'tmux'
a new session starts with no problem. I don't know about 'ssh-*' though.
With the diff I mailed we should be compatible with people who expect
/tmp to be a symbolic link for /var/tmp, but if we want to fix it for
good we should remove the other /var/tmp exceptions and warn users about
it.
