Am 26.07.2014 20:33, schrieb Michael Biebl: > As for .socket units: they should be treated like .service units and > started and stopped at the same time. > You just need to keep the ordering in mind. > If a package contains foo.service and foo.socket unit, you need to make > sure foo.socket is stopped before the foo.service (on remove/upgrade). > > I think that's all there is to it. > > I think it shouldn't be to hard to add.
Argh, actually, I spoke too soon. I completely forgot that we defer the actual start/stop/restart to invoke-rc.d in most cases (i.e. if there is a matching .service and SysV init script). So, yeah, we'd actually need to special case .socket units here or we change invoke-rc.d to actually stop .service *and* corresponding .socket files. Not quite sure yet, what the better approach is. Maybe this need a more interactive discussion on IRC or we hang out. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
