After a cursory scan of the Gentoo repository, I've noticed an
overabundance of start_stop_daemon_args being declared in scripts committed.
I would like to draw attention and see if we can clean these up together.
The reason why these are important is the modular nature of the
declarative syntax. For example, supervise-daemon should be available to
any user for a declarative script by simply adding
supervisor="supervise-daemon" to the corresponding conf.d file.
There are many necessary options like --wait or --env which don't have a
declarative replacement.
These comments are for scripts without a start/stop function defined
thereby relying on the default scripts in /lib/rc/sh/. There are other
advanced cases for sure. I just want to discuss easy to forget options.
Common mistakes included with start_stop_daemon_args:
"--background --make-pidfile" ("-b -m") should be replaced by
command_background="yes" (these are implied together)
"--user" and/or "--group" should be command_user="user:group" (use root
for user when only group is needed, the :group can be omitted)
"--chdir /path/to/foo" (-d) should be directory="/path/to/foo"
"--chroot /var/chroot/foo" (-r) should be chroot="/var/chroot/foo"
"--stdout /var/log/foo" (-1) should be output_log="/var/log/foo"
"--stderr /var/log/foo.err" (-2) should be error_log="/var/log/foo.err"
"--pidifle /run/foo.pid" (-p) should be pidfile="/run/foo.pid"
"--name foo" (-n) should be procname="foo"
"--exec" (-x) should be deleted as it is included by default when
command="" is declared (required to exist)
In addition, command_args may need to be reevaluated for each script to
split certain pieces out into command_args_foreground and
command_args_background.
command_args_foreground should include any options to force the
daemon/script into the foreground instead of forking.
command_args_background should include any option to fork a daemon and,
optionally, to have it write a pidfile to monitor. (Cannot be used
together with command_background option).
command_args should not include the conditions of the other two in most
cases.
If anyone would want me to do work in obvious cleanups, I am open to
bugs, patches or just committing.
Comments welcome.
Brian
overabundance of start_stop_daemon_args being declared in scripts committed.
I would like to draw attention and see if we can clean these up together.
The reason why these are important is the modular nature of the
declarative syntax. For example, supervise-daemon should be available to
any user for a declarative script by simply adding
supervisor="supervise-daemon" to the corresponding conf.d file.
There are many necessary options like --wait or --env which don't have a
declarative replacement.
These comments are for scripts without a start/stop function defined
thereby relying on the default scripts in /lib/rc/sh/. There are other
advanced cases for sure. I just want to discuss easy to forget options.
Common mistakes included with start_stop_daemon_args:
"--background --make-pidfile" ("-b -m") should be replaced by
command_background="yes" (these are implied together)
"--user" and/or "--group" should be command_user="user:group" (use root
for user when only group is needed, the :group can be omitted)
"--chdir /path/to/foo" (-d) should be directory="/path/to/foo"
"--chroot /var/chroot/foo" (-r) should be chroot="/var/chroot/foo"
"--stdout /var/log/foo" (-1) should be output_log="/var/log/foo"
"--stderr /var/log/foo.err" (-2) should be error_log="/var/log/foo.err"
"--pidifle /run/foo.pid" (-p) should be pidfile="/run/foo.pid"
"--name foo" (-n) should be procname="foo"
"--exec" (-x) should be deleted as it is included by default when
command="" is declared (required to exist)
In addition, command_args may need to be reevaluated for each script to
split certain pieces out into command_args_foreground and
command_args_background.
command_args_foreground should include any options to force the
daemon/script into the foreground instead of forking.
command_args_background should include any option to fork a daemon and,
optionally, to have it write a pidfile to monitor. (Cannot be used
together with command_background option).
command_args should not include the conditions of the other two in most
cases.
If anyone would want me to do work in obvious cleanups, I am open to
bugs, patches or just committing.
Comments welcome.
Brian
Attached Files:
-
OpenPGP_signature (0.82 KB)