[opensuse-factory] journald and syslog
Hi list, in openSUSE leap it's no longer possible to install a classic syslog daemon in addition to systemds journald. If I try i run into a package conflict. In my opinion this doesn’t make sense. Lot's of admins I know, want a classic syslog daemon because they know it and additional the the journald to learn how it works. What's about journalds "ForwardToSyslog" directive, if we can't use it? Sorry for my english... Stefan -- www.invis-server.org Stefan Schäfer Ludwigstr. 1-3 63679 Schotten -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Stefan, What is the bug number for this issue? If it's not reported, please do so, with exact error messages about the conflict. http://bugzilla.opensuse.org/enter_bug.cgi?product=openSUSE%20Distribution&f... Documentation: https://en.opensuse.org/openSUSE:Submitting_bug_reports On 21 October 2015 at 10:39, Stefan Schäfer <ml@fsproductions.de> wrote:
Hi list,
in openSUSE leap it's no longer possible to install a classic syslog daemon in addition to systemds journald. If I try i run into a package conflict.
In my opinion this doesn’t make sense. Lot's of admins I know, want a classic syslog daemon because they know it and additional the the journald to learn how it works.
What's about journalds "ForwardToSyslog" directive, if we can't use it?
Sorry for my english...
Stefan
-- www.invis-server.org
Stefan Schäfer Ludwigstr. 1-3 63679 Schotten
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 21.10.2015 um 11:10 schrieb Richard Brown:
Hi Stefan,
What is the bug number for this issue?
If it's not reported, please do so, with exact error messages about the conflict.
http://bugzilla.opensuse.org/enter_bug.cgi?product=openSUSE%20Distribution&f...
Documentation: https://en.opensuse.org/openSUSE:Submitting_bug_reports
On 21 October 2015 at 10:39, Stefan Schäfer <ml@fsproductions.de> wrote:
Hi list,
in openSUSE leap it's no longer possible to install a classic syslog daemon in addition to systemds journald. If I try i run into a package conflict.
In my opinion this doesn’t make sense. Lot's of admins I know, want a classic syslog daemon because they know it and additional the the journald to learn how it works.
What's about journalds "ForwardToSyslog" directive, if we can't use it?
Sorry for my english...
Stefan
-- www.invis-server.org
Stefan Schäfer Ludwigstr. 1-3 63679 Schotten
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Richard,
ok I report it as a bug. Stefan -- www.invis-server.org Stefan Schäfer Ludwigstr. 1-3 63679 Schotten -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mercredi 21 octobre 2015 à 10:39 +0200, Stefan Schäfer a écrit :
Hi list,
in openSUSE leap it's no longer possible to install a classic syslog daemon in addition to systemds journald. If I try i run into a package conflict.
In my opinion this doesn’t make sense. Lot's of admins I know, want a classic syslog daemon because they know it and additional the the journald to learn how it works.
What's about journalds "ForwardToSyslog" directive, if we can't use it?
You are incorrect here. Persistant journal on disk is enabled when /var/log/journal directory exists. This directory is packaged in systemd-logger package. This package is also providing "sysvinit(syslog)", to allow to uninstall any syslog implementation for people who wants to rely only on journal. systemd journald is ALWAYS installed and part of systemd package. All syslogs implementation packages are conflicting between each other (since you don't want to have syslog-ng and rsyslog running at the same time). This is why systemd-logger is conflicting with rsyslog (or syslog-nh). If you want both persistent journal AND rsyslog (ie basically writing logs twice), they can just install rsyslog and create /var/log/journal directory manually. But in your case, just install rsyslog, it will uninstall systemd-logger and you will just loose persistent journal, not journald. -- Frederic Crozat Enterprise Desktop Release Manager SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 21.10.2015 um 11:22 schrieb Frederic Crozat:
Le mercredi 21 octobre 2015 à 10:39 +0200, Stefan Schäfer a écrit :
Hi list,
in openSUSE leap it's no longer possible to install a classic syslog daemon in addition to systemds journald. If I try i run into a package conflict.
In my opinion this doesn’t make sense. Lot's of admins I know, want a classic syslog daemon because they know it and additional the the journald to learn how it works.
What's about journalds "ForwardToSyslog" directive, if we can't use it? You are incorrect here.
Persistant journal on disk is enabled when /var/log/journal directory exists. This directory is packaged in systemd-logger package. This package is also providing "sysvinit(syslog)", to allow to uninstall any syslog implementation for people who wants to rely only on journal.
systemd journald is ALWAYS installed and part of systemd package.
All syslogs implementation packages are conflicting between each other (since you don't want to have syslog-ng and rsyslog running at the same time). This is why systemd-logger is conflicting with rsyslog (or syslog-nh).
If you want both persistent journal AND rsyslog (ie basically writing logs twice), they can just install rsyslog and create /var/log/journal directory manually.
But in your case, just install rsyslog, it will uninstall systemd-logger and you will just loose persistent journal, not journald.
Thank's for that info. Stefan -- www.invis-server.org Stefan Schäfer Ludwigstr. 1-3 63679 Schotten -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-10-21 13:26, Stefan Schäfer wrote:
Am 21.10.2015 um 11:22 schrieb Frederic Crozat:
Le mercredi 21 octobre 2015 à 10:39 +0200, Stefan Schäfer a écrit :
...
Thank's for that info.
Yes, thanks a lot. I more or less knew it, but not clearly. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYnlxkACgkQtTMYHG2NR9U+9gCeK9apJbBOvTz5xjEaNe0W9cv9 iZcAn0ezHUWRwnTobdcy7HM2bOJVdSNj =0AXs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/21/2015 05:22 AM, Frederic Crozat wrote:
Le mercredi 21 octobre 2015 à 10:39 +0200, Stefan Schäfer a écrit :
Hi list,
in openSUSE leap it's no longer possible to install a classic syslog daemon in addition to systemds journald. If I try i run into a package conflict.
In my opinion this doesn’t make sense. Lot's of admins I know, want a classic syslog daemon because they know it and additional the the journald to learn how it works.
What's about journalds "ForwardToSyslog" directive, if we can't use it?
You are incorrect here.
Persistant journal on disk is enabled when /var/log/journal directory exists.
Starting with which version of systemd? -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mercredi 21 octobre 2015 à 10:45 -0400, Ken Schneider - Factory a écrit :
On 10/21/2015 05:22 AM, Frederic Crozat wrote:
Le mercredi 21 octobre 2015 à 10:39 +0200, Stefan Schäfer a écrit :
Hi list,
in openSUSE leap it's no longer possible to install a classic syslog daemon in addition to systemds journald. If I try i run into a package conflict.
In my opinion this doesn’t make sense. Lot's of admins I know, want a classic syslog daemon because they know it and additional the the journald to learn how it works.
What's about journalds "ForwardToSyslog" directive, if we can't use it?
You are incorrect here.
Persistant journal on disk is enabled when /var/log/journal directory exists.
Starting with which version of systemd?
Since 12.1 IIRC (and we had an issue there, because /var/log/journal was part of the main package, so upgrading to 12.2 was keeping /var/log/journal even if systemd-logger was not installed) -- Frederic Crozat Enterprise Desktop Release Manager SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Frederic Crozat <fcrozat@suse.com> writes:
Since 12.1 IIRC (and we had an issue there, because /var/log/journal was part of the main package, so upgrading to 12.2 was keeping /var/log/journal even if systemd-logger was not installed)
It will also be kept if it is non-empty, so the issue still exists. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le jeudi 22 octobre 2015 à 09:41 +0200, Andreas Schwab a écrit :
Frederic Crozat <fcrozat@suse.com> writes:
Since 12.1 IIRC (and we had an issue there, because /var/log/journal was part of the main package, so upgrading to 12.2 was keeping /var/log/journal even if systemd-logger was not installed)
It will also be kept if it is non-empty, so the issue still exists.
It was documented on 12.2 RN, IIRC. We don't want logs (ie user data) to be wiped-out during upgrade.. -- Frederic Crozat Enterprise Desktop Release Manager SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Frederic Crozat <fcrozat@suse.com> writes:
Le jeudi 22 octobre 2015 à 09:41 +0200, Andreas Schwab a écrit :
Frederic Crozat <fcrozat@suse.com> writes:
Since 12.1 IIRC (and we had an issue there, because /var/log/journal was part of the main package, so upgrading to 12.2 was keeping /var/log/journal even if systemd-logger was not installed)
It will also be kept if it is non-empty, so the issue still exists.
It was documented on 12.2 RN, IIRC. We don't want logs (ie user data) to be wiped-out during upgrade..
It just means that the existence of a directory is never a good way to trigger a service. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Andreas Schwab -
Carlos E. R. -
Frederic Crozat -
Ken Schneider - Factory -
Richard Brown -
Stefan Schäfer