Tong Sun <suntong...@users.sourceforge.net> writes:
>
> see if removing the added lines works for you
Yep, beaut, removing that works.
The messages slightly stack up. I wonder if that was the reason for the
--quiet stuff in the actual init-d-script, which I thought was hiding
information! Nothing to worry about though.
> I was forced to add them back because of the
>
> initd-script-does-not-implement-required-option &
> init.d-script-does-not-source-init-functions
Hmm. You can always stick a lintian override file in the package, to
mean vaguely you considered it and had good reason :-). Or ignore!
If it might be of interest, and since I mentioned having a go a long
time ago, for comparison
http://user42.tuxfamily.org/temporary/x2gpm.init
It's a slight cut and paste, but is all I understood needed at the time.
/etc/init.d has quite a few examples of varying levels of difficulty or
configability though :).
I'm a fork and make pidfile myself, so no --background which you have.
And being an executable I can match --exec in addition to the pidfile
for stop.
