On Mon, 2017-01-23 at 07:58 +0800, 積丹尼 Dan Jacobson wrote:
> BH> There is no log daemon for logger to talk to.
>
> Err... I mean talk to the same thing that is saving them up to put them
> into journalctl.
I think the only place available is the kernel log buffer.
Ben.
--
Ben Hutchings
Hoare's
BH> There is no log daemon for logger to talk to.
Err... I mean talk to the same thing that is saving them up to put them
into journalctl.
On Mon, 2017-01-23 at 02:30 +0800, 積丹尼 Dan Jacobson wrote:
> BH> initramfs-tools does not use systemd. If systemd is failing to log its
> BH> output at boot time, that is not a bug in initramfs-tools.
>
> OK I filed #852229 [systemd] failing to log output at boot time
>
> BH> (I recognise that
BH> initramfs-tools does not use systemd. If systemd is failing to log its
BH> output at boot time, that is not a bug in initramfs-tools.
OK I filed #852229 [systemd] failing to log output at boot time
BH> (I recognise that initramfs-tools should log output before it hands
BH> over to systemd (
On Sun, 2017-01-22 at 18:34 +0800, Dan Jacobson wrote:
> Package: initramfs-tools
> Version: 0.126
> Severity: wishlist
>
> You generate
> /run/initramfs/fsck-root
> /run/initramfs/fsck.log
> Good.
>
> Please also generate a similar log of the messages that the user sees
> fly by upon boot before
Package: initramfs-tools
Version: 0.126
Severity: wishlist
You generate
/run/initramfs/fsck-root
/run/initramfs/fsck.log
Good.
Please also generate a similar log of the messages that the user sees
fly by upon boot before the ones that are captured by journalctl.
Actually it turns out they are no
6 matches
Mail list logo
