And logging issues following F15B upgrade

[Lennart Poettering]

On Sun, 15.05.11 13:08, Philip Prindeville (philipp_subx at redfish-solutions.com) wrote:

> > Lennart
> 
> Ok, then I'm unclear.  Should rsyslog be running?
> 
> Because "chkconfig rsyslog --list" doesn't show any information, and
> it doesn't seem to be running after reboot.

The output this command generates should point you to the fact that the
--list command is not supported on systemd:

<snip>
Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by
      native
      systemd configuration.
</snip>

> # chkconfig rsyslog --add
> # chkconfig rsyslog on
> 
> doesn't seem to do anything.  Shouldn't it be on by default?

Yes, it should be on by default.

"systemctl enable rsyslog.service" or "chkconfig rsyslog on" should
ensure that.

When upgrading at the wrong time the conversion from sysv to systemd
might not work properly and the service is not enabled after the
upgrade. This should not be a problem however in the final release of
F15.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.