[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#316321: revisiting the "reload target" issue

On Thu, Jan 26, 2006 at 11:38:57AM -0500, sean finney wrote:
> severity 316321 serious
> tags 316321 patch
> thanks
> hi,
> revisiting this issue, and after having spoken with folks
> on -devel and -policy, the consensus is that this is in
> fact a policy violation, so i am changing the severity
> appropriately.
> but, because doing so merely to do so wouldn't be so
> constructive, i've also patched the init script to
> behave appropriately.  i've attempted to keep the
> patch as clean as possible... and have taken
> code that would otherwise be duplicated and
> placed them in common functions (apache_get_pid and 
> apache_kill).  
> here's some sample output of the new behavior:
> mini-me[~]17:34:55$ sudo /etc/init.d/apache2 start
> Starting apache 2.0 web server....
> mini-me[~]17:35:00$ sudo /etc/init.d/apache2 reload
> Reloading apache 2.0 configuration....
> mini-me[~]17:35:05$ sudo /etc/init.d/apache2 stop  
> Stopping apache 2.0 web server....
> mini-me[~]17:35:12$ sudo /etc/init.d/apache2 reload
> Reloading apache 2.0 configuration... no pidfile, not sending signal.  failed!

  Ping apache2-common maintainers ?

  is there any reason why that bug is rotting in a RC state for 4+
monthes ?

  I may perform an NMU soon.
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: signature.asc
Description: Digital signature

Reply to: