Hi Bruno, Am 07.04.2014 09:26, schrieb Bruno Friedmann:
Upstream have always promise that the journal has not problem, just the parser. So I keep them ;-)
I keep the messages-$DATE.xz, I know that I can read them without relying on someone else :-) Journal is just for "fun" (well, strange values of "fun") for now and the foreseeable future.
I'm using a poor dirty man hack rotate way. I've no formal code but my hack follow the idea of
Find journal storage D=$(journalctl --header --system | grep "Machine ID" | awk '{print $3}') R=${D}_$(date --utc "+%F_%H%M%S") $B="/var/log/journal"
systemctl stop systemd-journald.service mv ${B}/${D} ${B}/${R} systemctl start systemd-journald.service
That's cool. I'll keep that for reference :-)
Journal is recreated and old one are still accessible with journalctl --directory=PATH could be exported to another host etc...
Not that ideal as you can see, but I know that I don't have 100 lines of incoming logs when the rotate happen.
IMO you should be able to just move the directory and then restart journald, since the FDs will stay open during move, so you'll only have a very short outage? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org