[systemd-devel] [ANNOUNCE] systemd v38
Lennart Poettering
lennart at poettering.net
Wed Jan 11 07:02:36 PST 2012
On Wed, 11.01.12 08:04, Michael Biebl (mbiebl at gmail.com) wrote:
>
> Am 11. Januar 2012 05:19 schrieb Lennart Poettering <lennart at poettering.net>:
> > This is the first release with the journal. The journal replaces both
>
> A few observations/questions:
> - How can I check if XZ compression is enabled for the journal file
> (needless to say I enabled XZ support during compile time).
> The file seems to grow rather fast here (10 Mb after a few reboots).
Try:
ldd /lib/systemd/systemd-journald
which should tell you whether it links against libxz. XZ compression is
on by default. Note that compression only kicks in for larger fields.
> - /etc/systemd/systemd-journald.conf mentions system-journald.conf(5)
> but there is no such man page
Yupp, as mentioned documentation is terse right now...
> - I tried to enable rsyslog to test how well it works in combination
> with the journal. I used the aforementioned configuration to make it
> listen on /run/systemd/journal/syslog. And then symlinked
> /etc/systemd/system/syslog.service →
> /lib/systemd/system/rsyslog.service (as mentioned in syslog.socket).
> If I do that, running "logger foo" will make the message show up in
> the journal and /var/log/messages. So far so good.
> When I try to shutdown though, systemd get's stuck and I need to hit
> CTRL+ALT+DEL repeatedly to make it shutdown completely. I somehow
> suspect that redirecting the job output to syslog will trigger the
> start of rsyslog.service (when it's already been stopped) so it needs
> to be stopped again.
> That's only a guess though.
Hmm, there might be some problems remaining in that area, I'll have a
look.
Lennart
--
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel
mailing list