Hi Rafael, Rafael Zalamena wrote on Wed, Jul 02, 2014 at 02:21:25PM -0300:
> 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. While i don't consider linking /tmp and /var/tmp to each other a particularly good idea and expect people will encounter occasional trouble doing so, i'd rather not add even more stuff to the list of things that might break, unless for a good reason. Right now, people having separate /tmp and /var/tmp are not hurt by the /var/tmp exceptions: They simply won't have such files in /var/tmp. So i'd rather leave all the exceptions in place. It is also easier to maintain one consistent list (even two copies of it) that two subtly different lists. So, no further code change required unless i'm missing something. As for warning people: Both /tmp and /var/tmp are directories contained in the default install. It goes without saying that you shouldn't fiddle with them unless you know what you are doing and want the pain. The list of bad ideas you could come up with is infinite. We don't warn people either that moving all files from /bin to /usr/bin and deleting /bin is a bad idea, even though that is likely to hurt even more. Assuming that we don't *recommend* linking the two together somewhere, i don't see a documentation change that might be helpful. Yours, Ingo
