Re: init script output

2006-11-19 Thread Yaroslav Halchenko
well - status has being there for quite a while > invoke-rc.d fail2ban status Status of authentication failure monitor: fail2ban is running but the question is actually an attempt to disambiguate behavior/output of start/stop actions in cases when it was already started/stopped since there is no

Re: init script output

2006-11-19 Thread Jörg Sommer
Hello Yaroslav, Yaroslav Halchenko <[EMAIL PROTECTED]> wrote: >> I would, of course, prefer a solution with the lsb functions. What >> I want is to know when fail2ban started and when I accidentally >> tried to start it while the daemon was already running. > BTW - it seems that /etc/init.d/skelet

Re: init script output

2006-11-16 Thread Yaroslav Halchenko
> I would, of course, prefer a solution with the lsb functions. What > I want is to know when fail2ban started and when I accidentally > tried to start it while the daemon was already running. BTW - it seems that /etc/init.d/skeleton does not provide any additional status (which you requested), tha

Re: init script output

2006-11-16 Thread martin f krafft
also sprach Yaroslav Halchenko <[EMAIL PROTECTED]> [2006.11.16.1717 +0100]: > piper:~# /etc/init.d/apache2 start || echo failure > #[345] > Starting web server (apache2)... . > piper:~# /etc/init.d/apache2 start || echo failure > #[346] > Starting web s

init script output

2006-11-16 Thread Yaroslav Halchenko
Dear Mentors, Discussing a bug 398740 [1] I could not reach a settlement with the bug reported due to the fact that I could not find a clear statement in debian policy (although I think that I saw it somewhere and that is why init script now performs this way) or LSB about init script that " if da