Yaroslav Halchenko wrote: > Thank you Aaron, > > Indeed, standardization is a good thing and I thing the point when init > files format was changed and I missed --retry argument for > start-stop-daemon which is quite important for 'restart' on somewhat > slow boxes... Also I will include status action for the init script > since it comes handy > > what do you think would be more appropriate for sarge backports? > sarge ships with 2.0-7 lsb-base, so at lest log_daemon_msg is missing... > Thus there are 2 choices for sarge backports: > - ship with tuned new version of init.d which defines log_daemon_msg if > none is provided with lsb init-functions (simplest way I think, since > then I can depend on 2.0-7 version of lsb-bse and don't bother > keeping depends separate for sarge) > > - keep older version of init script, so I ship it with backports... > > what would be your recommendation?
I think maintaining just one version is better than maintaining two of them. Since there is already a backport of lsb-base (see backports.org) I would simply depend on lsb-base 3; the users wanting to install the fail2ban backport would have to install the lsb-base backport too. The postfix backport does it that way too. Greetings, Aaron -- Aaron Isotton | http://www.isotton.com/ I'll give you a definite maybe. --Samuel Goldwyn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
