https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |fcrozat@suse.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c1 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |fcrozat@suse.com, | |mt@suse.com InfoProvider| |fcrozat@suse.com --- Comment #1 from Dr. Werner Fink 2012-11-07 09:01:17 UTC --- The aim if to be able to use one systemd service file for syslog service or target and be able to switch on the fly between three syslog daemons, that is syslogd, syslog-ng, and rsyslog simply by changing SYSLOG_DAEMON in /etc/sysconfig/syslog. This was a major feature of SLES and it had worked flawless with SysVinit. Only with systemd there are problems with such a requirement. Maybe there is an other way to do this, e.g. with the help of a symbolic link. Or maybe systemd-195+ has some other new features now breaking the output of the generator script but be usable to switch on the fly between several syslogger with their different needs and approaches. -- 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.

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.

https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c5 --- Comment #5 from Dr. Werner Fink 2012-11-07 10:11:20 UTC --- Hmmm ... After stopping the syslog target I was able to use systemclt to re-run the generator script after stop and then start the syslog target with the new core again. Beside this... AFAIK the journal of systemd does not provide remote logging nor does it provide ASCII log files. Suppose you have a system crash that your mounting the root file system below /mnt with the help of a rescue disk. The binary journals below /var/log/journal/ will not help a lot ... on the other hand a ASCII file like /var/log/messages and /var/log/warn will do. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c7 --- Comment #7 from Dr. Werner Fink 2012-11-07 10:38:45 UTC --- (In reply to comment #6) Does this mean that journalctl now has an option --root to be able to do e.g. journalctl --root /mnt --all ... indeed that would be perfect. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c9 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|werner@suse.com |mt@suse.com --- Comment #9 from Marius Tomaschewski 2012-11-07 15:47:31 UTC --- Raymond, thanks for you submission requests! I've rejected the syslog-ng changes and forward of rsyslog to factory for now, but I'll merge them as needed: Yes, we will switch to use xyzsyslog.sevice with syslog.service alias, but this has to be done more carefully. Werner, I'm reassigning to me. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c11 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #11 from Marius Tomaschewski 2012-11-08 15:45:33 UTC --- (In reply to comment #10)

I agree with the above discussion to start using aliases although I still fail to see the need to switch system loggers on the fly.

Yes. I've to look more exactly what the macros are doing --> tomorrow. I've revoked rsyslogd & syslogd (syslog-ng follows), see work-in-progress: $OBS/home:mtomaschewski:branches:Base:System/ -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c13 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #13 from Marius Tomaschewski 2012-11-13 09:26:07 UTC --- It is IMO fixed now in these requests: 141086 syslogd -> openSUSE:Factory 141070 rsyslog -> openSUSE:Factory 141076 syslog-ng -> Base:System (will be forwarderd) On factory, you need the syslog-service package which is build inside of syslogd. To enable a syslog service, install the rsyslog/syslogd/syslog-ng package and call "systemctl enable <syslog daemon name>.service", see syslog(8). Then you can start/stop it using the syslog.service alias. AFAIS, there is currently no preset file in factory which would do it. Please reopen when the same problem occurs with the fixed version. BTW: For 12.1,2 and SLE-11-SP2, there are "inofficial backport" packages in $OBS/home:mtomaschewski:syslog, which need syslog-service as released. That is, don't install the factory syslog-service on versions < 12.3. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c15 --- Comment #15 from Bernhard Wiedemann 2012-11-14 14:44:00 CET --- This is an autogenerated message for OBS integration: This bug (788330) was mentioned in https://build.opensuse.org/request/show/141141 https://build.opensuse.org/request/show/141144 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c17 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rschweikert@suse.com --- Comment #17 from Marius Tomaschewski 2012-11-22 13:04:40 UTC --- *** Bug 790293 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=790293 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=788330 https://bugzilla.novell.com/show_bug.cgi?id=788330#c19 --- Comment #19 from Marius Tomaschewski 2012-11-22 17:20:30 UTC --- Ahm... I've still got the same problem with rsyslogd.service. The reason were, that unlike the shell, systemd seems to expands ${FOO} as "" (empty argument) and $FOO as empty string, when the variable is empty. I overlooked this before :-( Resubmitted rsyslog and syslogd packages. -- 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.