On 06/19/2014 10:45 PM, Debian Bug Tracking System wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package mai
Michael
can you use adm group instead of systemd-journal?
adm is traditionaly used to allow people to read logs. i've open an
upstream bug regarding that.
https://bugzilla.redhat.com/show_bug.cgi?id=1047729
--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
__
Am 19.06.2014 18:18, schrieb Lionel Elie Mamane:
> Package: systemd
> Version: 204-8
> Severity: normal
>
> Just switched to systemd (installed systemd-sysv), on an up-to-date
> jessie system.
>
> On reboot, I notice:
>
> Jun 19 17:53:02 fort systemd-fsck[959]: /dev/mapper/fort-root is mounted.
Package: systemd
Version: 204-8
Severity: normal
Just switched to systemd (installed systemd-sysv), on an up-to-date
jessie system.
On reboot, I notice:
Jun 19 17:53:02 fort systemd-fsck[959]: /dev/mapper/fort-root is mounted.
Jun 19 17:53:02 fort systemd-fsck[959]: e2fsck: Cannot continue, abor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: systemd
Version: 204-10
Doing a fork and becoming a daemon process are not the same.
Something like "Type=forking" in the *.service file is
ambiguous. Does systemd provide a controlling terminal to
the ExecStart job that has to be dropped,
