[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: init.d script dependencies for etch?

also sprach Bastian Blank <waldi@debian.org> [2005.04.01.2031 +0200]:
> |         # Make networking dependency conditional on configuration
> |         case $(sed 's/#.*//' /etc/syslog-ng/syslog-ng.conf) in
> |                 *source*tcp*|*source*udp*|*destination*tcp*|*destination*udp*)
> |                         need net ;;
> |         esac
> | 
> |         need clock hostname
> |         provide logger

Uh, this looks like a "pull" type of thing in which ever init.d
script starts its dependencies. I don't think this is a good idea.

After all, the main reason why we want dependencies is to be able to
parallelise the startup process. If we do that, we will run into
locking problems trying to keep track which dependencies have been
started and which not. Or we make other packages assume too much
information about a given dependencies (e.g. by requiring a /bin/ps

Please do not send copies of list mail to me; I read the list!
 .''`.     martin f. krafft <madduck@debian.org>
: :'  :    proud Debian developer, admin, user, and author
`. `'`
  `-  Debian - when you have better things to do than fixing a system
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
"the difference between genius and stupidity
 is that genius has it's limits."
                                                    -- albert einstein

Attachment: signature.asc
Description: Digital signature

Reply to: