Hello:
At my organization, there can be hundreds of user logins in a
public workstation each day, among more than one thousand of users.
Since each user login produces a 8MiB sparse log file in
/var/log/journal/xxxxx/, significant disk space is consumed. From the
administrator point of view, it is desirable to prioritize system log
over user log. For example, when total log size exceeds SystemMaxUse,
user log is vacuumed / rotated before system log. Can we achieve this
goal under current implementation?
I guess the size of pre-allocation (in my case, 8MiB), is probably
determined platform-wise. Here[1] I include some relevant platform info
that might aids debugging.
Many thanks!
[1]
https://www.csie.ntu.edu.tw/~yunchih/s/systemd-journald-sample-output.log
--
Yun-Chih Chen 陳耘志
Network/Workstation Assistant
Dept. of Computer Science and Information Engineering
National Taiwan University
Tel: +886-2-33664888 ext. 217/204
Email: ta...@csie.ntu.edu.tw
Website: http://wslab.csie.ntu.edu.tw/
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
