Hello.
Sorry if what I ask is very silly, but I feel I need to ask anyway...
If sysvinit started syslog and waited for it and then started
everything else, why can't we do the same with systemd?
I mean, don't create the socket and then start syslog, but just
start syslog and make everything that logs wait for it like in sysvinit.
Is this just a performance optimization or is there another reason?
BTW, my system says "systemd-journal[153]: Forwarding to syslog
missed 293 messages.".
Another thing I don't understand is why after startup, in normal
operation, things like NetworkManager or some other daemons can lose
messages to syslog? Does that happen with sysvinit too or is it a
systemd specific thing?
RHEL7 has the same issue? Maybe they have solved it or do something
differently, but it could be useful to look...
Thanks and sorry for being dumb!
Have a great day!
--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: iba...@codigolibre.net - http://go.to/ibaldo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
