Author: jajcus Date: Mon May 10 08:53:13 2010 New Revision: 11412 Modified: rc-scripts/branches/upstart_native/doc/upstart.txt Log: - 'upstart_controlled --except' documentation
Modified: rc-scripts/branches/upstart_native/doc/upstart.txt ============================================================================== --- rc-scripts/branches/upstart_native/doc/upstart.txt (original) +++ rc-scripts/branches/upstart_native/doc/upstart.txt Mon May 10 08:53:13 2010 @@ -170,10 +170,17 @@ Sometimes some commands must be implemented in a special way (not all services may understand SIGHUP as a signal to reload their configuration) or extra -commands are provided (like 'configtest'). In such case 'upstart_controlled' -should be given a list of commands to implement. If the first argument of the -script was not one of the listed commands, processing will continue past -'upstart_controlled' call and the commands may be handled by the init script. +commands are provided (like 'configtest'). In such case ``upstart_controlled`` +should be given a list of commands to implement or, preferrably, ``--except`` +and the list of commands which stay implemented in the script. If the first +argument of the script is one to be of the 'not upstart_controlled' commands, +processing will continue past 'upstart_controlled' call and the commands may +be handled by the init script. + +When ``configtest`` is includes in the ``upstart_controlled --except`` list +then ``$script configtest`` will be called before each restart/reload attempt, +but only when done by ``/sbin/service`` or call to the script. Direct initctl +calls are not affected. The minimal init script, for a service which will be controlled by upstart only would be:: _______________________________________________ pld-cvs-commit mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
