Thomas Hood <[EMAIL PROTECTED]> said: > We are talking here, after all, about how invoke-rc.d handles an > invalid setup.
Well, but making this invalid setup a "locally valid" one by defining the most useful invoke-rc.d behavior for it is one of two ways to solve the (otherwise still unsolvable, right?) administrative problem of making a service manually controlled. I guess implementing the other potential solution (making the K->K transition do nothing) probably has as many or even more side effects. > For packages with maintainer scripts that do "invoke-rc.d restart" or > equivalent, the multiuser runlevel directories must contain either an > S or a K symlink. This will remain true even when #243159 is > implemented. Must this be so? As long as the no-S-and-K-links situation is officially undefined, it wouldn't do any harm to let invoke-rc.d actually do a "try-restart" when called with "restart" and no links exists, would it? Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
