[Pkg-sysvinit-devel] Two line init.d scripts? Sure, that will work!
Sergey B Kirpichev
skirpichev at gmail.com
Thu Feb 6 10:32:21 UTC 2014
> I think this illustrates nicely the problem with this approach:
> - there are two lines, which contain code.
> - there are five commented lines, which are interpreted and contain important data.
> - and there are four lines of commented code, which are mostly comments, except two.
And yet another one:
- there are many people in the Debian, who are not aware about LSB at all...
(I'm not surprised, that among tech-ctte members too...)
> I don't think it's worse pushing this confusing "solution" out to hundreds of
> packages, especially since superior solutions exists.
For example? (And please keep away systemd/upstart/etc propaganda from
this thread, it's all about sysvinit only.)
Peter, thank you for your work. Have you tried any complex init
script to fit this business (apache2 or postfix, for example)?
BTW, I don't think your postfix script is an actual replacement for the
current init-script. For example, there are create_xconsole() and sendsigs_omit()
functions. Also, there is the do_rotate function - a very common example
when you want to implement a custom action (not just one from fixed set
Also, you should keep in mind this scenario as well:
Last but not least, we can utilize custom lsb-headers (X-Debian-* like) to
keep information like pidfile or daemon binary path name. I think,
there is a parser for this LSB-info somewhere in the lsb-* packages.
More information about the Pkg-sysvinit-devel