On Tue, 07.05.13 13:15, Umut Tezduyar (u...@tezduyar.com) wrote:
Hi,
No worries. Maybe you want to add systemd-journal-flush.service to
man systemd-journald.
I have now added a TODO list item, so that we don't forget to properly
document systemd-journal-flush.service.
Lennart
--
Lennart
Hi,
No worries. Maybe you want to add systemd-journal-flush.service to
man systemd-journald.
Maybe altering the help text as following too:
To make the data persistent it is sufficient to create /var/log/journal/
where systemd-journald-flush.service will then store the data.
On Mon, May 6,
Hi,
I have masked the systemd-journal-flush.service and set the
Storage=persistent in journald.conf. Then I have removed the
/var/log/journal folder. My expectation on next boot was to see the journal
files in /var/log/journal but they have stayed in /run/log/journal.
According to man journald,
On Mon, 06.05.13 12:41, Umut Tezduyar (u...@tezduyar.com) wrote:
Hi,
I have masked the systemd-journal-flush.service and set the
Storage=persistent in journald.conf. Then I have removed the
/var/log/journal folder. My expectation on next boot was to see the journal
files in
On Mon, 06.05.13 22:39, Lennart Poettering (lenn...@poettering.net) wrote:
According to man journald, it shouldn't be necessary to send the SIGUSR1 as
systemd-journal-flush.service does. It was my expectation that systemd
would eventually carry journal to /var/.
The man page is actually
