Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1072209 > unrolled thread

Bug#925473: tomcat9: sysvinit script missing

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#925473: tomcat9: sysvinit script missing Ondrej Zary <ondrej@zary.sk> - 2021-09-21 12:40 +0200
    Bug#925473: tomcat9: sysvinit script missing Emmanuel Bourg <ebourg@apache.org> - 2021-09-21 16:40 +0200
    Bug#925473: tomcat9: sysvinit script missing Thorsten Glaser <t.glaser@tarent.de> - 2021-09-21 18:20 +0200
      Bug#925473: tomcat9: sysvinit script missing Markus Koschany <apo@debian.org> - 2021-09-21 21:30 +0200
        Bug#925473: tomcat9: sysvinit script missing Thorsten Glaser <tg@mirbsd.de> - 2021-09-21 21:50 +0200
      Bug#925473: tomcat9: sysvinit script missing Ondrej Zary <ondrej@zary.sk> - 2021-09-24 12:10 +0200

#1072209 — Bug#925473: tomcat9: sysvinit script missing

Hello,
why tomcat9 still does not have an init script despite it has been posted here?

I'm upgrading a Stretch server without systemd to Buster. Tomcat 9 is installed but cannot be started without an init script.

-- 
Ondrej Zary

[toc] | [next] | [standalone]

#1072233

Hi Ondrej,

Installing systemd should fix this issue.

Emmanuel Bourg


Le 2021-09-21 12:23, Ondrej Zary a écrit :
> Hello,
> why tomcat9 still does not have an init script despite it has been 
> posted here?
> 
> I'm upgrading a Stretch server without systemd to Buster. Tomcat 9 is
> installed but cannot be started without an init script.

[toc] | [prev] | [next] | [standalone]

#1072249

Ondrej Zary dixit:

>Hello, why tomcat9 still does not have an init script despite it has
>been posted here?
>
>I'm upgrading a Stretch server without systemd to Buster. Tomcat 9 is
>installed but cannot be started without an init script.

Mostly because Emmanuel insists on using systemd’s abstraction to
create the user account, despite a working, tested, alternative I
offered to maintain and be responsible for exists.

The “sysvinit” branch contains a working version of the package
which I update from time to time. I’m also publishing builds of
that here:

http://www.mirbsd.org/~tg/Debs/dists/bullseye/lts/Pkgs/tomcat9/

This is the “wtf-lts” repo on Wouter’s extrepodata.

The package contains the init script, the user management logic
that actually works across *all* *supported* Debian configurations
instead of just an *arbitrary* subset of those, and some instructions
for nōn-systemd users in logging.properties (the default logging is
configured for systemd) and README.Debian (specifically noting that
some of the applied hardening is systemd-specific, but compared to
stretch/sysvinit you’re not worse off, security-wise, so…).

I have no idea why Emmanuel, the primary maintainer, has been set
so strongly against merging this patch for as long as I promise to
take care of it and deal with any related fallout (maybe some systemd
fan paid him) but this is what is, and that GR outcome is interpreted
as Emmanuel being able to block this indefinitely despite nōn-systemd
continuing to be a supported way of running Debian (albeit not without
UsrMove in bookworm/sid).

bye,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

[toc] | [prev] | [next] | [standalone]

#1072267

[Multipart message — attachments visible in raw view] — view raw

Am Dienstag, dem 21.09.2021 um 16:10 +0000 schrieb Thorsten Glaser:
[...]
> I have no idea why Emmanuel, the primary maintainer, has been set
> so strongly against merging this patch for as long as I promise to
> take care of it and deal with any related fallout

>  (maybe some systemd
> fan paid him)

^^^ 
Such malicious allegations are not helpful.

>  but this is what is, and that GR outcome is interpreted
> as Emmanuel being able to block this indefinitely despite nōn-systemd
> continuing to be a supported way of running Debian (albeit not without
> UsrMove in bookworm/sid).

The GR outcome was systemd but we support exploring alternatives, not we
support systemd and sysvinit in any case. Systemd is far superior when it comes
to security features like sandboxing and limiting access to the file system.
This is not a theoretical problem. Tomcat has been affected by security
vulnerabilities like remote code execution and read and write access to
arbitrary files in the past. Just focusing on systemd makes it simpler for us
to support Tomcat for its whole life cycle which is at least five years. These
are the main reasons for not supporting sysvinit.

[toc] | [prev] | [next] | [standalone]

#1072268

Markus Koschany dixit:

>>  (maybe some systemd
>> fan paid him)
>
>^^^
>Such malicious allegations are not helpful.

You should adjust your humour detector.

>>  but this is what is, and that GR outcome is interpreted
>> as Emmanuel being able to block this indefinitely despite nōn-systemd
>> continuing to be a supported way of running Debian (albeit not without
>> UsrMove in bookworm/sid).
>
>The GR outcome was systemd but we support exploring alternatives, not we
>support systemd and sysvinit in any case.

It wasn’t we desupport sysvinit either.

>Systemd is far superior when it comes
[…]

That may very well be, but OUR PRIORITIES ARE OUR USERS AND FREE SOFTWARE
(Debian SC), and if the user requires to run sysvinit but wishes to run
tomcat as well, it is MASSIVELY outside of the scope of the tomcat main‐
tainers to force people to switch the entire way of how the system is set
up, booted and administered!

The security implications are documented in the branch. This is enough.
We sell rope, after all. (Or perhaps more, ahem, politely: PHP is also
still packaged in Debian, despite its security history which is also not
a theoretical problem. Sorry for singling you out, PHP, but I needed an
example.)

bye,
//mirabilos
-- 
“ah that reminds me, thanks for the stellar entertainment that you and certain
other people provide on the Debian mailing lists │ sole reason I subscribed to
them (I'm not using Debian anywhere) is the entertainment factor │ Debian does
not strike me as a place for good humour, much less German admin-style humour”

[toc] | [prev] | [next] | [standalone]

#1072741

On Tuesday 21 September 2021, Thorsten Glaser wrote:
> Ondrej Zary dixit:
> 
> >Hello, why tomcat9 still does not have an init script despite it has
> >been posted here?
> >
> >I'm upgrading a Stretch server without systemd to Buster. Tomcat 9 is
> >installed but cannot be started without an init script.
> 
> Mostly because Emmanuel insists on using systemd’s abstraction to
> create the user account, despite a working, tested, alternative I
> offered to maintain and be responsible for exists.
> 
> The “sysvinit” branch contains a working version of the package
> which I update from time to time. I’m also publishing builds of
> that here:
> 
> http://www.mirbsd.org/~tg/Debs/dists/bullseye/lts/Pkgs/tomcat9/
> 
> This is the “wtf-lts” repo on Wouter’s extrepodata.
> 
> The package contains the init script, the user management logic
> that actually works across *all* *supported* Debian configurations
> instead of just an *arbitrary* subset of those, and some instructions
> for nōn-systemd users in logging.properties (the default logging is
> configured for systemd) and README.Debian (specifically noting that
> some of the applied hardening is systemd-specific, but compared to
> stretch/sysvinit you’re not worse off, security-wise, so…).
> 
> I have no idea why Emmanuel, the primary maintainer, has been set
> so strongly against merging this patch for as long as I promise to
> take care of it and deal with any related fallout (maybe some systemd
> fan paid him) but this is what is, and that GR outcome is interpreted
> as Emmanuel being able to block this indefinitely despite nōn-systemd
> continuing to be a supported way of running Debian (albeit not without
> UsrMove in bookworm/sid).

Thank you.
I simply put your init script manually into /etc/init.d/
Also added /usr/libexec/sysv-getjre.sh and /usr/libexec/sysv-start.sh and
changed formatter in logging.properties. Now Tomcat 9 works fine.

Fortunately, Debian tomcat9 package does not depend on systemd-sysv. So systemd is installed but it does no harm as it's not running.

-- 
Ondrej Zary

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web