Tollef Fog Heen <[email protected]> writes: > ]] Russ Allbery > (Cleaned up the Cc line somewhat)
>> You can do quite a bit with the hooks that are part of the specification >> of both types of files. For example, logic that you may add to control >> whether the service should start at all can be implemented by adding a >> pre-start stanza to the upstart configuration. > ExecStartPre=/bin/false > will make the service be considered failed. The ExecStartPre line can > of course be an executable that implements more checking or logic. Ah, thank you! I got lost in the systemd.* man pages and didn't find the systemd.service one somehow (even though it's right there listed first; sigh). ExecStartPre and ExecStartPost add most of the functionality that I wasn't seeing in other examples. It's a bit awkward compared to the upstart script directive since you have to externalize the shell script somewhere or write inline shell in a rather irritating format, but that's really a minor complaint. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
