Opened bug report at mainstream.
https://github.com/systemd/systemd/issues/12498
On Tue, May 7, 2019 at 12:17 PM Peter Viskup wrote:
> It is related to systemd processing of chroot, as with commenting the User
> setting, the service start up successfully.
>
> Want to mimic the startup of the ser
It is related to systemd processing of chroot, as with commenting the User
setting, the service start up successfully.
Want to mimic the startup of the service in init script on Debian8 (which
is running fine):
~# start-stop-daemon --start --quiet --pidfile
"/srv/inst/var/run/rsyslogd.pid" --chuid
On Tue, May 07, 2019 at 11:08:38AM +0200, Peter Viskup wrote:
> Running Debian9 with systemd 241-3~bpo9+1 from backports.
> Having trouble to start rsyslog service in chroot jail using the systemd
> service file with RootDirectory and User settings.
> Setting AmbientCapabilities=CAP_SYS_CHROOT does
Running Debian9 with systemd 241-3~bpo9+1 from backports.
Having trouble to start rsyslog service in chroot jail using the systemd
service file with RootDirectory and User settings.
Setting AmbientCapabilities=CAP_SYS_CHROOT does not help and still getting
following errors:
rsyslog-chroot@inst.se
4 matches
Mail list logo