On 12.7.2019 11.19, Emmanuel Bourg wrote:
> Le 12/07/2019 à 09:31, Aki Tuomi a écrit :
>
>> Seems that this can be worked around with setting during installation
>> SYSTEMCTL_INSTALL_CLIENT_SIDE=1 SYSTEMCTL_FORCE_BUS=1 SYSTEMD_OFFLINE=1
> As I understand from the systemd documentation [1] this
Le 12/07/2019 à 09:31, Aki Tuomi a écrit :
> Seems that this can be worked around with setting during installation
> SYSTEMCTL_INSTALL_CLIENT_SIDE=1 SYSTEMCTL_FORCE_BUS=1 SYSTEMD_OFFLINE=1
As I understand from the systemd documentation [1] this disables the
interactions with PID 1, so I guess it
On 11.7.2019 18.01, Markus Koschany wrote:
> Hello,
>
> this issue is caused by the command systemctl daemon-reload in
> solr-tomcat's postinst file. You can try to remove it and see if it
> works. However solr-tomcat is supposed to work in a systemd environment,
> I doubt that anyone has tested
Hello,
this issue is caused by the command systemctl daemon-reload in
solr-tomcat's postinst file. You can try to remove it and see if it
works. However solr-tomcat is supposed to work in a systemd environment,
I doubt that anyone has tested it with another init system or without one.
Regards,
Package: solr-tomcat
Version: 3.6.2+dfsg-20
I am building docker image with solr-tomcat inside using Debian Buster.
When installing solr-tomcat in Dockerfile, installation fails because
Setting up solr-tomcat (3.6.2+dfsg-20) ...
System has not been booted with systemd as init system (PID 1).
5 matches
Mail list logo