[arch-general] Huge log file for SLiM

C Anthony Risinger anthony at xtfx.me
Wed Jul 4 05:41:06 EDT 2012


On Wed, Jul 4, 2012 at 3:13 AM, Alexandre Isoard
<alexandre.isoard at ens-lyon.fr> wrote:
>
> Read man pages of systemd. This will avoid a lot of struggling.
>
> From "man 8 systemd-journald":
>
>> By default the journal stores log data in /run/log/journal/. Since
>> /run/ is volatile log data is lost at reboot. To make the data
>> persistent it is sufficient to create /var/log/journal/ where
>> systemd-journald will then store the data.
>
> systemd-journald automatically replace syslog-ng.
> And the new way of consulting logs is by using journalctl.

unless this changed in the last few weeks since i fixed it, systemd
will whine if you don't have syslog.service set to *something*.
journald is nice, but where is it designated as a complete
replacement?  i read some stuff about git/hash-chains (which is great,
btw), but my [brief] expedition did not produce a clear message one
way or the other.

i did however surface these ...

# pacman -Qql systemd | xargs zgrep syslog.service

# vim /usr/lib/systemd/system/syslog.socket
----------------------------------------------
[...]
    The default syslog implementation should make syslog.service a
    symlink to itself, so that this socket activates the right actual
    syslog service.

    Examples:

    /etc/systemd/system/syslog.service -> /lib/systemd/system/rsyslog.service
    /etc/systemd/system/syslog.service -> /lib/systemd/system/syslog-ng.service
[...]
----------------------------------------------

# man 7 systemd.special
----------------------------------------------
[...]
       syslog.service
           The syslog service if any. Implementations should create a symlink
           from the actual syslog implementation to this generic name for
           activating it.

       syslog.socket
           The socket unit where syslog implementations should listen on. All
           userspace log messages will be made available on this socket.
[...]
----------------------------------------------

... current-gen syslog daemons have many useful features/extensions
and i expect will be supported for quite some time (if the intent is
to 100% displace them) ... journald also has some great features, but
they don't appear to be a superset of the traditional daemons AFAICS.

-- 

C Anthony


More information about the arch-general mailing list