Hello again.
i sent a signal with sudo kill -s SIGUSR2 pid# but the folder containing
the journal didn't come down to 30M as i was expecting.
also:
sudo systemctl status systemd-journald.service
systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service;
static)
Active: active (running) since Wed, 2012-11-28 13:46:02 EET; 3min
0s ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 178 (systemd-journal)
Status: "Processing requests..."
CGroup: name=systemd:/system/systemd-journald.service
└─178 /usr/lib/systemd/systemd-journald
Nov 28 13:46:02 mainland systemd-journal[178]: Journal started
Nov 28 13:46:02 mainland systemd-journal[178]: Allowing system journal
files to grow to 30.0M.
Warning: Journal has been rotated since unit was started. Log output is
incomplete or unavailable.
Could it be that there are files left in the folder from undeleted
previous rotations or something like that??
Also it seems that it erases files from a date back -when i observed
this i had files from October but now those have gone- but it just
doesn't seem to respect the size.
Thanks.
Apostolos B.
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
