05.03.2016 11:55, Carlos E. R. пишет:
On 2016-03-05 09:30, Carlos E. R. wrote:
On 2016-03-05 08:19, Andrei Borzenkov wrote:
04.03.2016 21:05, Carlos E. R. пишет:
Yes, I found that one, but seemed not to work.
That would be a bug.
Maybe... but I'm at 13.1.
"none" was present in Storage option from the very beginning and appeared in systemd v186. Which version in in 13.1? Does it recognize Storage=none but it does not work, or does it not understand Storage option at all?
Version 208. I'm unsure at this moment what failed, but I had to try several options and restart the journal service several times till it obeyed and purged the log. It was deleted entirely, not trimmed to the 50 MB I requested.
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? :) 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.
It is possible that when I wrote that it did not work I was referring to the options I used limiting size: I specified 100 or 50 MB, yet the log had 300MB, in tmpfs, thus RAM. At the end it worked, though. The files were not purged to specified size, but deleted completely and log restarted.