Comment 1 for bug 94873

The way in which I've been thinking of doing this is to permit the job to define custom actions (in addition to those built-in during the usual job cycle).

These actions would be permitted to be run while the job is running, and would receive the current pid as an environment variable, etc.

If you look at the upstart code, you'll see that most of the support is already there for this and it just needs completing.

In particular, the syntax for specifying them in the configuration file.