tmux leaves a socket behind in /tmp/tmux-1000/default on exit. It should
remove sockets that it created after it stops listening on them and then
rmdir the tmux-$uid directories that it created.

Hi Paul,

Thanks for the report. I discussed this with upstream and we agree that
this is probably not worth fixing. Removing the server socket on exit
would be easy, but removing the directory would not because the deletion
can race with the startup of another server; doing this properly would
require some synchronization logic and since this is just cosmetic, we
think it's not worth the effort.

So I'm tagging this wontfix for now.

Cheers,

With /run/user/$UID around, how about moving the socket there?

Regards,
Ondrej

Hello,

Good morning,

We have gone through your samples from a partner and Here is our  Order
List. Please do bear in mind that we are very much in  need of this
order, quote your competitive prices.

Kindly send the Order confirmation.

Your early reply will be much appreciated.

Best Regards,

Maryanah Erwin.

PT FINDORA INTERNUSA

Jln Pahlawan 66 Kec. Arjawinangun

45162 CIREBON West-Java INDONESIA

tel : +62 231 357334

fax: +62 231 357260

email: marketing@findora.com

Hi,

I have noticed that when there is no tmux session then the command
	$ tmux ls
gives
	$ no server running on /run/user/1000/tmux-1000/default

So it appears that a tmux-1000/default is expected.

Therefore the issue is not that ``tmux leaves a socket behind behing it'',
but exactly the contrary: tmux needs to leave a socket behind behing it.

Best wishes,
Jerome

Hi,

contrary to Jerome's mail, on my Trixie system tmux is not interested in
/run/user.

~$ tmux ls
no server running on /tmp/tmux-501/default

IMHO it'd be a very good idea to either patch tmux, or ship an
/etc/profile.d/tmux.sh file that sets TMUX_TMPDIR to /run/user/$(id -u).
Long-term files under /tmp risk deletion, these days.