> > > 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
Thanks, from that POV it makes sense. I'm not good at re-assigning debian bugs could one of you please do so to affect system as well?
