Bug#291148: [PROPOSAL] Add a 'status' option in init.d scripts

2008-06-13 Thread Dustin Kirkland
On Fri, 24 Jun 2005 21:21:57 -0700, Matt Zimmerman <[EMAIL PROTECTED]> wrote: > I agree with Manoj's suggestion. The best way to go about it would be to > draft a complete proposal (including standardizing the output format), start > patching packages in unstable, and go from there. Please see th

Bug#291148: [PROPOSAL] Add a 'status' option in init.d scripts

2005-06-25 Thread Matt Zimmerman
I agree with Manoj's suggestion. The best way to go about it would be to draft a complete proposal (including standardizing the output format), start patching packages in unstable, and go from there. FWIW, I think it would be appropriate to add an option to start-stop-daemon to support this use c

Re: Bug#291148: [PROPOSAL] Add a 'status' option in init.d scripts

2005-06-24 Thread Manoj Srivastava
On Fri, 24 Jun 2005 18:24:56 +0200, Bill Allombert <[EMAIL PROTECTED]> said: >> I think rather than trying to decree a policy, and over engineer an >> optional action for an init script meant mostly for user >> consumption, we should let the developers come up with whatever >> works best for the

Bug#291148: [PROPOSAL] Add a 'status' option in init.d scripts

2005-06-24 Thread Bill Allombert
On Tue, Jun 21, 2005 at 04:10:53PM -0500, Manoj Srivastava wrote: > On Tue, 21 Jun 2005 21:57:35 +0200, <[EMAIL PROTECTED]> said: > > > On Wed, Jan 19, 2005 at 01:30:55AM +0100, Javier Fernández-Sanguino Peña > > wrote: > >> --- policy.sgml.orig 2005-01-19 01:10:37.0 +0100 > >> +++ pol

Bug#291148: [PROPOSAL] Add a 'status' option in init.d scripts

2005-06-21 Thread Manoj Srivastava
On Tue, 21 Jun 2005 21:57:35 +0200, <[EMAIL PROTECTED]> said: > On Wed, Jan 19, 2005 at 01:30:55AM +0100, Javier Fernández-Sanguino Peña > wrote: >> --- policy.sgml.orig 2005-01-19 01:10:37.0 +0100 >> +++ policy.sgml 2005-01-19 01:13:05.0 +0100 >> @@ -5392,13 +5392,17 @@ force-

Bug#291148: [PROPOSAL] Add a 'status' option in init.d scripts

2005-06-21 Thread allomber
On Wed, Jan 19, 2005 at 01:30:55AM +0100, Javier Fernández-Sanguino Peña wrote: > --- policy.sgml.orig 2005-01-19 01:10:37.0 +0100 > +++ policy.sgml 2005-01-19 01:13:05.0 +0100 > @@ -5392,13 +5392,17 @@ > force-reload > cause the configuration to be r

Re: Bug#291148: [PROPOSAL] Add a 'status' option in init.d scripts

2005-01-19 Thread Jamin W. Collins
On Wed, Jan 19, 2005 at 11:34:24PM +0100, Bill Allombert wrote: > On Wed, Jan 19, 2005 at 10:56:57PM +0100, Thomas Hood wrote: > > > > "/etc/init.d/foo start" should exit with a nonzero status if foo failed > > to start. Unfortunately this status isn't conveyed to the user, as you > > say. > > T

Re: Bug#291148: [PROPOSAL] Add a 'status' option in init.d scripts

2005-01-19 Thread Bill Allombert
On Wed, Jan 19, 2005 at 10:56:57PM +0100, Thomas Hood wrote: > > "/etc/init.d/foo start" should exit with a nonzero status if foo failed > to start. Unfortunately this status isn't conveyed to the user, as you > say. That is not exactly true: See 9.4. Console messages from `init.d' scripts In p

Re: Bug#291148: [PROPOSAL] Add a 'status' option in init.d scripts

2005-01-19 Thread Thomas Hood
On Wed, 19 Jan 2005 02:00:18 +0100, Javier Fernández-Sanguino Peña wrote: > I would like a new option to be added to init.d scripts: 'status' > which basicly tells what status is the service currently in > (either running or dead). This wish combines nicely with the wish that initscripts implem

Bug#291148: [PROPOSAL] Add a 'status' option in init.d scripts

2005-01-18 Thread Javier Fernández-Sanguino Peña
Package: debian-policy Version: 3.6.1.1 Priority: wishlist Tags: patch [ Note: I understand that this status suggestion is covered (without a valid example in #208010) but I believe that LSB compliance also forces some other things (like exit codes) which is still under discussion. That's why I'm