Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER

2007-08-12 Thread Javier Kohen
El mié, 01-08-2007 a las 07:49 +0200, Michael Koch escribió: tag 425020 patch thanks On Fri, May 18, 2007 at 03:10:13PM +0200, Javier Kohen wrote: Package: tomcat5.5 Version: 5.5.20-4 Severity: normal I noticed that leaving TOMCAT5_USER empty in /etc/default/tomcat5.5 is not

Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER

2007-08-02 Thread Michael Koch
tag 425020 pending thanks On Wed, Aug 01, 2007 at 11:12:01PM +0200, Michael Koch wrote: On Wed, Aug 01, 2007 at 07:01:41PM +0200, Marcus Better wrote: David Pashley wrote: I still think the documentation is wrong and that if you want to disable tomcat at boot then you should disable it

Processed: Re: Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER

2007-08-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tag 425020 pending Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER Tags were: patch Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator

Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER

2007-08-01 Thread David Pashley
I still think the documentation is wrong and that if you want to disable tomcat at boot then you should disable it in your rc.d system. Seems pointless is implementing yet another scheme for disabling tomcat. Changing rc.d also has the advantage that you can just start it manually without having

Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER

2007-08-01 Thread Marcus Better
David Pashley wrote: I still think the documentation is wrong and that if you want to disable tomcat at boot then you should disable it in your rc.d system. I tend to agree. And I think the current behaviour is correct - if the TOMCAT5_USER variable is empty, the init script must provide a

Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER

2007-08-01 Thread Michael Koch
On Wed, Aug 01, 2007 at 07:01:41PM +0200, Marcus Better wrote: David Pashley wrote: I still think the documentation is wrong and that if you want to disable tomcat at boot then you should disable it in your rc.d system. I tend to agree. And I think the current behaviour is correct - if the

Processed: Re: Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER

2007-07-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tag 425020 patch Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator

Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER

2007-07-31 Thread Michael Koch
tag 425020 patch thanks On Fri, May 18, 2007 at 03:10:13PM +0200, Javier Kohen wrote: Package: tomcat5.5 Version: 5.5.20-4 Severity: normal I noticed that leaving TOMCAT5_USER empty in /etc/default/tomcat5.5 is not preventing the launcher from starting Tomcat during boot. This was working

Bug#425020: tomcat5.5: Does not honor empty TOMCAT5_USER

2007-05-18 Thread Javier Kohen
Package: tomcat5.5 Version: 5.5.20-4 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I noticed that leaving TOMCAT5_USER empty in /etc/default/tomcat5.5 is not preventing the launcher from starting Tomcat during boot. This was working with Tomcat 5.0 in Debian. The current init