On Feb 13, 2013, at 10:29 PM, Lennart Poettering wrote:
systemd.journald.forward_to_console=1
This is exactly what I was after - thanks everybody
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
On Wed, Feb 13, 2013 at 10:56 AM, Thierry Parmentelat
thierry.parmente...@inria.fr wrote:
Thanks for the feedback; I didn't know that, so it might come in handy in
understanding the problem
However, I'm puzzled because it looks like there's no attempt at all to
launch pl_sysinit
The
Hi Kay; thanks for taking the time to write this down
I understand what you guys are saying; and at first sight I am on the safe side
here though (as the name suggests, pl_sysinit will only mount filesystems and
init network interfaces and the like)
However your answers do not shed any light
'Twas brillig, and Thierry Parmentelat at 13/02/13 14:03 did gyre and
gimble:
Hi Kay; thanks for taking the time to write this down
I understand what you guys are saying; and at first sight I am on the
safe side here though (as the name suggests, pl_sysinit will only
mount filesystems and
On Wed, 13.02.13 10:56, Thierry Parmentelat (thierry.parmente...@inria.fr)
wrote:
Hi Lennart
Thanks for the feedback; I didn't know that, so it might come in handy in
understanding the problem
However, I'm puzzled because it looks like there's no attempt at all to
launch pl_sysinit
On Feb 13, 2013, at 4:41 PM, Lennart Poettering wrote:
Log output of services ends up in the journal these days, from both
early boot and late boot. And used to end up in syslog, except for
early-boot where it ended up in kmsg -- which is probably what you saw.
hence, check syslog or
On Feb 13, 2013, at 9:26 PM, Thierry Parmentelat wrote:
Right now I'm using
systemd.log_level=debug systemd.log_target=kmsg
OK, of course, I should use log_target=console
Which I just did, and that shows a brief mention to pl_sysinit:
About to execute /etc/init.d/pl_sysinit^M
Forked
On Wed, 13.02.13 21:26, Thierry Parmentelat (thierry.parmente...@inria.fr)
wrote:
On Feb 13, 2013, at 4:41 PM, Lennart Poettering wrote:
Log output of services ends up in the journal these days, from both
early boot and late boot. And used to end up in syslog, except for
early-boot
On Feb 13, 2013, at 10:29 PM, Lennart Poettering wrote:
Hmm? Why does syslog/journalctl require the network?
Yeah, sorry, I haven't made myself very clear: I can't get into the node as I
have no physical access; and the node can't talk on the network; so I can't see
the output of either of
On Mon, 11.02.13 13:37, Thierry Parmentelat (thierry.parmente...@inria.fr)
wrote:
Hi
Feel free to redirect me to some other place if needed :)
So, we have a BootCD that is intended for remotely managed machines
In a nutshell, we need to redefine the whole init sequence, and what we had
Hi
Feel free to redirect me to some other place if needed :)
So, we have a BootCD that is intended for remotely managed machines
In a nutshell, we need to redefine the whole init sequence, and what we had on
f12 and f14 boxes was essentially a set of 2 init scripts, one for rough system
11 matches
Mail list logo
