Le mercredi 25 janvier 2012 à 11:24 +0100, Peter Czanik a écrit :
On 01/25/2012 10:22 AM, Frederic Crozat wrote:
Le mardi 24 janvier 2012 à 21:09 +0100, Peter Czanik a écrit :
On 01/24/2012 03:02 PM, Frederic Crozat wrote:
Le mardi 24 janvier 2012 à 14:51 +0100, Peter Czanik a écrit :
On 01/24/2012 02:43 PM, Andreas Jaeger wrote:
> journal is part of systemd and will be enabled. > > It doesn't change anything to *syslog*, compared to older systemd > release : as long as *syslog* implementation were using .service and > socket activated (this should be ok since 12.1, see > http://www.freedesktop.org/wiki/Software/systemd/syslog but I'm not sure > data there is up to date with journal ), they will still work as > expected, with data from journal being forwarded to *syslog* through > syslog socket. So, what you're saying is that journal is an additional logger that will run in parallel with the "normal" syslog.
From my understanding, "normal" syslog is not installed any more by default. It is only needed if central log collection is necessary, as journal is a local only solution. Or if advanced features, like launching external applications, logging to a database, parsing messages, etc. are necessary. It is still installed by default, nothing has changed in that regard (unless somebody changed default openSUSE installed without tell us ;)
Strange. From my understanding journal was developed to make normal syslog redundant on most machines. Does it also mean, that messages will be archived twice, once by journal in its secure log database and also by syslog text files? Well, I'd be happy to not ship a syslog implementation by default, but not until we have removed sysvinit (otherwise, people booting on sysvinit won't have any logs..). Could it be solved by adding syslog as a dependency to sysvinit-init?
I guess it could be a possibility. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org