Booted today into new stable kernel and see using $> less /var/log/rc.log this now: *^O Starting smartd ... [ ok ]^O *^O /var/run/tor: creating directory *^O /var/run/tor: correcting owner *^O Starting tor ... [ ok ]^O *^O Starting local ... [ ok ]^O rc default logging stopped at Sun Mar 25 11:01:42 2018 Where does the escape sequence ^O come from?
That is coming from your terminal's "me" termcap sequence. "me" is used to reset SGR attributes (bold, color, etc) back to default. ^O is the Shift-In character, which is used by ISO-2022 supporting terminals to ensure you're back on the G0 character set (the main one, typically ASCII). I'm wondering if we shouldn't just have rc-logger strip all non-printable characters, in addition to escapes and CSI sequences (which it already strips).
(In reply to dwfreed from comment #1) FWIW this happens just now, not before the ncurses/kernel update.
This will be included in OpenRC 0.36. https://github.com/openrc/openrc/commit/2b1392af
I will be taking back this commit, it seems to create issues when shutting down.
The following commit fixes this and will be in OpenRC 0.36. https://github.com/openrc/openrc/commit/7e56a49e
