Bug#672361: bootlogd: escape sequences should be filtered out

[Vincent Lefevre]

On 2019-08-06 15:10:25 +0000, Dmitry Bogatov wrote:
> [2012-05-20 11:37] "Marc Dequènes (Duck)" <duck at duckcorp.org>
> > Coin,
> >
> > Fancy output should be deactivated or handled differently, but we  
> > really need the ok/fail/warn status displayed properly. Having the  
> > result of escape commands would be easier to parse than just removing  
> > escape codes ("[ok] stuff" instead of "[....] stuff ok").
> 
> Nowdays bootlogd filters-out escape characters, so closing bug. I
> believe it was introduced in 2.91.

Filtering out escape characters is useless without filtering out
the whole escape sequence. Actually, this is even worse, as this
prevents the escape sequences from being interpreted by the
terminal.

> I agree, that "[..] stuff ok" is not very readable, but it is not
> reasonable to expect bootlogd to actually interpret control sequences.

Then it should not filter out anything.

> I think it should be fixed in bin:lsb-base by changing style of
> decoration: placing [ok] at end of line, not beginning.

Now that systemd became the default, the problem has been solved by
using it instead of sysvinit + bootlogd: a /var/log/boot.log file is
generated where nothing is filtered out, so that the file is readable
with "cat" or "less" (and text is colored).

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)