The Samba-Bugzilla – Bug 12435
leaking files under private/msg.sock and var/lock/msg.lock
Last modified: 2016-11-18 16:59:45 UTC
Reproduction: start samba, and then shut it down, you will see a bunch of files are left behind under private/msg.sock and var/lock/msg.lock. I've reproduced it on a illumos/opensolaris platform, haven't tried on Linux.
Samba has provisions to clean up both directories regularly. Is it a major problem for you that we leave sfome files behind? Will they pile up indefinitely, or are they disappearing again when you restart Samba and what a while?
If it is a major showstopper for you, can you try to find out which daemons leave something behind?
With best regards,
... who feels shitty having changed messaging at all. Sockets seemed to be a good idea, but they are just not reliable enough for production.
It's not a blocker for us, I just feel the cleanup is not working properly. It seems the number of files piles up, and won't go away even after shutting down Samba.
I will try to figure out which daemon leaves those files behind when I get a chance.
(In reply to Volker Lendecke from comment #1)
> ... who feels shitty having changed messaging at all. Sockets seemed to be a
> good idea, but they are just not reliable enough for production.
Nah, don't feel bad. We can't go back to tdb messaging. Making all the code signal-safe is a harder task than fixing socket issues, and I'm not sure we ever had it right.
Files left behind is a very minor issue compared with sig-safe code issues :-).