Somewhat unexpected; is it really intentional?
{pts/1}% systemctl status alsa.service
alsa.service - LSB: Launch alsa sound system
Loaded: loaded (/etc/rc.d/init.d/alsa)
Active: active (exited) since Sun, 23 Jan 2011 17:53:39
+0300; 47min ago
CGroup: name=systemd:/sys
On Sun, Jan 23, 2011 at 00:01, Tom Gundersen wrote:
> Further to my previous mail about hwclock, I'm struggling to get my
> head around what is the "proper" way to handle hwclock's adjfile.
>
> These are my assumptions:
>
> /etc is in principle mounted read-only (not yet possible, but that's
> the
On Sat, Jan 22, 2011 at 21:44, Tom Gundersen wrote:
> I'm trying to figure out how our hwclock handling works, and in
> particular if there are any scenarios we don't handle.
>
> First, I think there is a typo in the explanation given in
> hwclock-load.service. Is the attached patch correct?
>
> S
On Sun, Jan 23, 2011 at 12:22, Andrey Borzenkov wrote:
> Could someone clarify what is supposed to be standard syslog
> integration in systemd? I.e. am I right, that
>
> - syslog.socket activates built-in systemd syslog implementation
> systemd-kmsg-syslogd which simply dumps everything to /dev/km
Could someone clarify what is supposed to be standard syslog
integration in systemd? I.e. am I right, that
- syslog.socket activates built-in systemd syslog implementation
systemd-kmsg-syslogd which simply dumps everything to /dev/kmsg
- at some point "real" syslog service is started which either
