On Wed, 2010-04-07 at 15:39 +0000, Thomas Krause wrote:
> sudo initctl reload network-interface
>
> gives me the message
>
> initctl: Unknown parameter: INTERFACE
>
> Obviously the "network-interface" job is able to detect unset parameters
> instead of destroying everything.
>
Yeah, I was just thinking about this over a cup of tea. instance jobs
already have mandatory parameters, since they're required to determine
which instance it is.
It makes sense to extend this to tasks as well, which require
environment from their events. Even /etc/init/rc.conf technically
requires RUNLEVEL be set.
If we handle this at the Upstart-level, it makes more sense. So
something like:
On Wed, 2010-04-07 at 15:39 +0000, Thomas Krause wrote:
> sudo initctl reload network-interface
>
> gives me the message
>
> initctl: Unknown parameter: INTERFACE
>
> Obviously the "network-interface" job is able to detect unset parameters
> instead of destroying everything.
>
Yeah, I was just thinking about this over a cup of tea. instance jobs
already have mandatory parameters, since they're required to determine
which instance it is.
It makes sense to extend this to tasks as well, which require
environment from their events. Even /etc/init/rc.conf technically
requires RUNLEVEL be set.
If we handle this at the Upstart-level, it makes more sense. So
something like:
# start mounted-tmp
start: Missing argument: MOUNTPOINT
Then you're more likely to do:
# start mounted-tmp MOUNTPOINT=/tmp
Scott
--
Scott James Remnant
<email address hidden>