From what I understood Option 1 has also been implemented as an alternative to
https://bugzilla.novell.com/show_bug.cgi?id=788330
https://bugzilla.novell.com/show_bug.cgi?id=788330#c3
--- Comment #3 from Raymond Wooninck 2012-11-07 09:46:52 UTC ---
The approach created with a script (that is only run on startup) to be able to
switch on the fly does not work.
I can indeed switch system loggers on the fly just by installing another one.
However the generator is not run until I reboot the system. Therefore the
on-the-fly principle doesn't really fly.
The only proper approach to this would be to have the service files included in
the separate syslog packages and to adjust the %post part to start directly the
new logger.
But switching on the fly would mean that for a small period of time, there is
no system logging at all. I wonder if this is really something that happens on
a running productive server ??
At this moment I see two approached that would make things work:
1) Utilize the journal of systemd which provides exactly the same logging as
the mentioned sysloggers. To me it seems to be the better choice as that I can
determine what I want to see when I call journalctl. With the other loggers, I
have to go through it with an editor.
2) Patch rsyslog, syslog-ng, syslogd to use the systemd-service file that
comes with the package to ensure that each one of the loggers has the correct
service file. The %post part of each package should then contain a particular
code to enable the systemd-service file and directly start the service. The
%preun part of the package should stop the service.
At this moment I have patched rsyslog and syslog-ng to come with their own
systemd service file and I have validated that both works. Both I have
submitted to Base:System. Unfortunately I didn't adjust the %post part yet so
that the service is directly started after installation. I have to check with
Frederic on that part.
the existing loggers. Systemd provides now a syslog package that just works
with the journal.
I will talk to Frederic and validate what the best way is to directly start a
service after installation.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.