On 2016-03-05 10:01, Andrei Borzenkov wrote:
05.03.2016 11:55, Carlos E. R. пишет:
I have activated Storage=none in this laptop and restarted journal service. I see in journalctl output:
Mar 05 09:49:53 minas-tirith.valinor systemd[1]: Stopping Journal Service... Mar 05 09:49:53 minas-tirith.valinor systemd-journal[254]: Journal stopped
But:
minas-tirith:~ # journalctl --disk-usage Journals take up 6.4M on disk. minas-tirith:~ #
So it is probably working here, but not completely as I expected.
I do not follow here - journald is stopped by works? :)
Yes, it apparently keeps the entries entered previous to stopping. Maybe after a reboot it disappears completely.
Anyway - I would expect that with Storage=none journald does not care about any existing data at all. So whatever you have there will remain (forever) unless you delete data yourself.
Yes, just my thought. You see, the main problem for me was that the non-persistent logs are written to disk in tmpfs (/run), up to 400MB (filled 300MB in six days), and for me having the logs in RAM is a waste of RAM that I can put to much better uses. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)