Hi, On Wed, Apr 01, 2020 at 03:21:57PM +0200, Christian Ehrhardt wrote: > > So the problem seems to be that systemd prints that warning whenever you > > try to restart a socket activated service that is already active and also > > backed by a .service unit - and it doesn't matter whether it's activated > > by socket or via the service file). > > > > Does that make sense? > > Almost :-) > Hi Guido, > > I like to summarize this from another POV: > - services can start and restart no matter what state the .socket files are in > - sockets can start if the service isn't up yet > - sockets can start if the service is and the socket is already up (is > just a no-op) > - restart = stop+start > > IMHO that just means we might want to "start" .socket files but never > ever "restart" them.
I initially thought the same but then we wouldn't make changes to .socket file effective until reboot so it looks to me as if systemd should handle this gracefully. -- Guido > > I'm in a bad position to decide if that means to better fix it in:: > A) debhelper: generate it differently into maintainer scripts > B) systemd: make systemctl "restart" *.socket behave like "start" > > I think if there is a corner case left that makes "systemctl restart > socket" needed (and I can think of a few) then the fix might be better > in debhelper. > But that discussion is exactly why I filed this bug - so thanks for chiming > in. >
