Update early logger logging path after remounting root as rw

2020-09-05 Thread Rio Liu
Hello people I'm configuring my linux to use s6-rc. It works fairly well so far. One thing I want to improve though, is that the early logger logs to /run/uncaught-logs. It's nice to have a log file during early boot and it helped my debugging easier. But it would be cool to able to change the loc

Re: Update early logger logging path after remounting root as rw

2020-09-05 Thread Laurent Bercot
I'm configuring my linux to use s6-rc. It works fairly well so far. One thing I want to improve though, is that the early logger logs to /run/uncaught-logs. It's nice to have a log file during early boot and it helped my debugging easier. But it would be cool to able to change the location to a

Re: Update early logger logging path after remounting root as rw

2020-09-05 Thread Rio Liu
> > Well the catch-all logger is supposed to be just that: a catch-all > logger. That means that ideally, every service should have its own > dedicated logger, typically writing to /var/log/something, and the > catch-all logger is only used for exceptional stuff such as error > messages from the su

Re: Update early logger logging path after remounting root as rw

2020-09-05 Thread Casper Ti. Vector
On Sat, Sep 05, 2020 at 11:46:44AM -0400, Rio Liu wrote: > I'm configuring my linux to use s6-rc. It works fairly well so far. One > thing I want to improve though, is that the early logger logs to > /run/uncaught-logs. It's nice to have a log file during early boot and it > helped my debugging eas

Re: Update early logger logging path after remounting root as rw

2020-09-05 Thread Samuel Holland
On 9/5/20 3:26 PM, Rio Liu wrote: >> >> Well the catch-all logger is supposed to be just that: a catch-all >> logger. That means that ideally, every service should have its own >> dedicated logger, typically writing to /var/log/something, and the >> catch-all logger is only used for exceptional stu

Re: Update early logger logging path after remounting root as rw

2020-09-06 Thread yianiris
The way I understand the importance of the catch-all log is to be able to debug the system that fails to boot. It is writing a log in /run even before a real filesystem is mounted. At this point the system should give access to this file even if root is not mounted as rw yet. There may be many wa

Re: Update early logger logging path after remounting root as rw

2020-09-06 Thread Rio Liu
Thanks for all the replies :) > Your requirements of saving logs from /run/uncaught-logs and (mentioned > later) batch-producing `producer-for'/`consumer-for' files can be > automated using slew: . (Other > encapsulations of s6/s6-rc also exist, but I am the