Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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.
In the man page? Obviously not, it's just a service unit.
Unless you mean that the "-u" option is documented, --since= is also documented, and from there deduce the whole line above,
I meant that the journalctl man-page describes the -u and the --since and -- until arguments.
and that it contains the entire output that the cron "mail" would have.
No, I don't see that described, I did realise that's what you were asking.
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.
I would certainly prefer that no system log data be available to an ordinary user. /Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org