On Sat, 2013-01-05 at 20:53 +0400, Andrey Borzenkov wrote:

I know. Do you mean that it is intended behavior and every user of 12.3 is going to get non-persistent logging by default? I don't know - I'll let the systemd guys answer that.

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Sat, 05 Jan 2013 16:28:43 -0300 Cristian Rodríguez пишет:

El 05/01/13 13:53, Andrey Borzenkov escribió:

...

...

If you create the directory /var/log/journal/ then you should get a persistent journal. I have not tried this myself.

persistent logging is provided by package systemd-logger

Which is not present after installation. So I repeat my question - is every 12.3 user going to have non-persistent logging after installation until (s)he manually adjusts system settings? Is this intentional? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 06/01/13 03:18, Andrey Borzenkov escribió:

So I repeat my question - is every 12.3 user going to have non-persistent logging after installation until (s)he manually adjusts system settings? Is this intentional?

No, package systemd-logger should get installed automatically in the case of a fresh install. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Le dimanche 06 janvier 2013 à 20:25 +0400, Andrey Borzenkov a écrit :

On Sun, Jan 6, 2013 at 6:49 PM, Cristian Rodríguez wrote:

...

El 06/01/13 03:18, Andrey Borzenkov escribió:

...

So I repeat my question - is every 12.3 user going to have non-persistent logging after installation until (s)he manually adjusts system settings? Is this intentional?

No, package systemd-logger should get installed automatically in the case of a fresh install.

OK, actually it does nothing beyond creating /var/log/journal. And rsyslog was installed but disabled.

By having /var/log/journal created, it means journal data will be persistent and journalctl output will be persistent (and no longer restricted to current boot session). -- Frederic Crozat SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 07/01/13 15:13, dieter escribió:

I am not aware I ever activated systemd journal,

You did not activated, it is mandatory for proper functioning of systemd. journalctl does not

exist on the systems. Log information is also written to /var/log/messages.

This is because your previous install has syslog, existing syslog installations are not modified in anyway.

/var/log/messages is properly rotated, the /var/log/journal/*/ are huge files and seem unrotated. These systems were updated from 12.1 with zypper dup.

The journal does rotate files, according to the configuration options ystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= see http://www.freedesktop.org/software/systemd/man/journald.conf.html -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 05/01/13 16:18, Carlos E. R. escribió:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

El 2013-01-05 a las 10:37 -0600, Michael Catanzaro escribió:

...

syslog was dropped since it's redundant with the journal. But I guess

Since when? The agreement as I remember was to keep it.

Syslog has not been dropped, it is not part of the default desktop installation. That is provided by the journal now. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 05.01.2013 20:18, schrieb Carlos E. R.:

El 2013-01-05 a las 10:37 -0600, Michael Catanzaro escribió:

...

syslog was dropped since it's redundant with the journal. But I guess

Since when? The agreement as I remember was to keep it.

it does not matter since it does not work since > 4 weeks anyway: susi:~ # rcsyslog start redirecting to systemctl start syslog Failed to issue method call: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details. susi:~ # systemctl status syslog.service syslog.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) So we should be honest and drop it. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 06.01.2013 16:23, schrieb Cristian Rodríguez:

El 06/01/13 12:09, Stefan Seyfried escribió:

...

susi:~ # systemctl status syslog.service syslog.service Loaded: error (Reason: No such file or directory) Active: inactive (dead)

the syslog unit should be provided with a syslog implementation..

susi:~ # rpm -qa *syslog* syslog-service-2.0-764.2.noarch syslog-ng-3.3.7-2.2.x86_64 -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 06.01.2013 16:43, schrieb Christian Boltz:

Hello,

Am Sonntag, 6. Januar 2013 schrieb Stefan Seyfried:

...

susi:~ # rcsyslog start redirecting to systemctl start syslog Failed to issue method call: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details. susi:~ # systemctl status syslog.service syslog.service Loaded: error (Reason: No such file or directory) Active: inactive (dead)

So we should be honest and drop it.

Sounds like https://bugzilla.novell.com/show_bug.cgi?id=790805

Symptom: /etc/systemd/system/multi-user.target.wants/syslog.service is a broken symlink pointing to a non-existant file.

Solution: systemctl enable rsylsog.service (or whatever syslog you prefer)

Thanks, that actually helped (with syslog-ng.service in my case).

Better solution: get a working upgrade path that automatically fixes the symlink

Absolutely necessary IMVHO. I mean -- i'm really systemd-friendly, but that everything gets broken all the time by the systemd migration and nobody cares for fixing it up is really annoying and makes me want to stop using it as in real life the benefits of systemd vs. sysvinit are nothing that you'd notice as a normal user. Thanks again, Stefan -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 06/01/13 12:09, Stefan Seyfried escribió:

Am 05.01.2013 20:18, schrieb Carlos E. R.:

...

El 2013-01-05 a las 10:37 -0600, Michael Catanzaro escribió:

...

syslog was dropped since it's redundant with the journal. But I guess

Since when? The agreement as I remember was to keep it.

it does not matter since it does not work since > 4 weeks anyway:

susi:~ # rcsyslog start redirecting to systemctl start syslog Failed to issue method call: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details.

Check your system.. find -L /etc/systemd -type l will tell you what service units went broken on upgrade. (they are pointing to /lib/ instead of /usr/lib) remove the dangling symlinks and run systemctl reenable on the services you want running again. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 01/09/2013 08:03 PM, Linda Walsh wrote:

Michael Catanzaro wrote:

...

syslog was dropped since it's redundant with the journal. But I guess Lennart probably(?) expects distros to enable persistent journaling if they're going to drop syslog.

---

I guess they are also porting over the existing syslog-ng filters so established system-monitoring tools built on such will continue working?

Syslog-ng works fine together both with systemd and sysvinit. You can check my latest syslog-ng 3.4rc1 packages from https://build.opensuse.org/project/show?project=home%3Aczanik%3Asyslog-ng34 . It should be part of Factory later this week. You can check what's new at http://bazsi.blogs.balabit.com/2012/12/syslog-ng-3-4beta1-released/ (rc1 just adds a couple of bugfixes). Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org