Teodor MICU wrote:
>[...]
>
> PS: how can I receive any responses on this bug without CC:me ?
>
Hi
I believe [1] will do the trick.
~Niels
[1] http://www.debian.org/Bugs/Developer#subscribe
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe
Hello,
On Tue, Mar 2, 2010 at 1:07 AM, Ludovic Claude
wrote:
> The changes were motivated by the fact that jscv is unreliable (see
> #561559) and is hard to use when you need to setup Tomcat with ports <
> 1024. Upstream maintains the catalina.sh script and recommends its use.
> We were kindly as
The changes were motivated by the fact that jscv is unreliable (see
#561559)
Nahh. I see that quite often without jsvc too, with upstream's startup
scripts.
Cheers,
Marcus
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Hello Teodor,
The changes were motivated by the fact that jscv is unreliable (see
#561559) and is hard to use when you need to setup Tomcat with ports <
1024. Upstream maintains the catalina.sh script and recommends its use.
We were kindly assisted by a Tomcat expert (Jason Brittain from
MuleSoft)
Package: tomcat6
Version: 6.0.24-2
Severity: grave
Justification: renders package unusable
Hi,
After todays upgrade to v6.0.24-2 due to migration to 'testing' the tomcat6
service
doesn't start anymore. I've tried a fresh install and there is no difference.
I see that 'jscv' is no longer used and
5 matches
Mail list logo