[Pkg-systemd-maintainers] Bug#738207: systemd-sysv: sockets are not removed after being stopped

Andreas Cadhalpun andreas.cadhalpun at googlemail.com
Sun Feb 9 10:17:36 GMT 2014


Hi Zbyszek,

thanks for this link.
So the reason for this behavior is explained by Lennart Poettering as:

"Consider this: a service A.service uses a socket A.socket. Now both are 
started, and then you stop A.socket but A.service continues to run. I 
think in that case the service should have every right to continue use 
it, and we shouldn't break its current usage. In fact I think I 
originally deleted those sockets, but ran into a problem with the 
deletion behaviour which is why added this comment. Don't remember the 
problem in question however."

Indeed I think this is a valid reason not to remove the socket file.
But the services (like avahi-daemon) I was thinking about have 
'Requires=avahi-daemon.socket' and thus it really does not make any 
sense to leave the socket file, when the socket is closed, because the 
service does *not* continue to run.

Is it possible to automatically remove the socket file in those cases, 
but not in the others?

Best regards,
Andreas




More information about the Pkg-systemd-maintainers mailing list