On Mon, 10.11.14 20:30, Alexandre Detiste ([email protected]) wrote:
> >> Yes, but then the log appears as a ugly big chunck without the
> >> timestamp & host on the left;
> > > except the first line. Is it ok to reopen /dev/ksmg for each line
> > > writen to avoid this ?
> >
> > Not s
>> Yes, but then the log appears as a ugly big chunck without the
>> timestamp & host on the left;
> > except the first line. Is it ok to reopen /dev/ksmg for each line
> > writen to avoid this ?
>
> Not sure I follow?
This might be a trivial problem; it's just that there are really few people
w
On Mon, 10.11.14 17:38, Alexandre Detiste ([email protected]) wrote:
> Le lundi 10 novembre 2014, 14:32:49 Lennart Poettering a écrit :
> > > I know that generators should log to /dev/kmsg during early boot.
> >
> > Correct!
>
> Yes, but then the log appears as a ugly big chunck withou
Le lundi 10 novembre 2014, 14:32:49 Lennart Poettering a écrit :
> > I know that generators should log to /dev/kmsg during early boot.
>
> Correct!
Yes, but then the log appears as a ugly big chunck without the timestamp & host
on the left;
except the first line. Is it ok to reopen /dev/ksmg fo
On Fri, 07.11.14 20:59, Alexandre Detiste ([email protected]) wrote:
> Hi,
>
> I know that generators should log to /dev/kmsg during early boot.
Correct!
> But, when they are restarted later by systemcl daemon-reload;
> is it better to write to the journal instead, by using systemd-ca
Hi,
I know that generators should log to /dev/kmsg during early boot.
But, when they are restarted later by systemcl daemon-reload;
is it better to write to the journal instead, by using systemd-cat for example ?
Or is it racy/forbidden ?
Greetings,
Alexandre Detiste
___
