On Thu, 24 Mar 2016 21:49, Carlos E. R. wrote:
On Thursday, 2016-03-24 at 21:34 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On Thursday, 2016-03-24 at 19:58 +0300, Andrei Borzenkov wrote:
24.03.2016 15:58, Carlos E. R. пишет:
What would be the procedure to obtain that ouput? That is, the "journalctl" options needed to obtain that output.
journalctl -u logrotate.service --since="..." --until="..." ...
It is even described in "man journalctl" ...
Not in mine :-)
I guess your systemd is pre-195? The man page in 12.3 has the description.
I have 13.1 (210), and search for "logrotate" finds nothing. Unless you mean that the "-u" option is documented, --since= is also documented, and from there deduce the whole line above, and that it contains the entire output that the cron "mail" would have.
The examples section in the manual is exceedingly short.
Even then I find difficult how to produce the output of a particular logrotate session. First you have to find out when it did run. Fortunately, 13.1 doesn't use this new method.
Another completely separate question - it seems to me that journalctl gives any ordinary user access to (what would otherwise be) log data? That's not good. I guess journalctl ought to be only accessible by root?
Not complete access. Some entries you can read, some you can't. I haven't figured out which entries I get or how to change the behaviour, because I typically add my admin user to the root group in order to be able to read the logs as that user.
Hint on that: look at "ls -l /run/log/journal/*/" most often there are some bits for access missing, or just set wrong. - Yamaban