On Wed, Dec 11, 2019 at 12:28 PM Adam Williamson
<adamwill(a)fedoraproject.org> wrote:
On Wed, 2019-12-11 at 14:11 -0500, pmkellly(a)frontier.com wrote:
> The test case is running on a new install. During the install a user was
> set up and that user has Admin. In that situation I've never had
> problems running journalcrl, grep, or this journalctl | grep. Perhaps we
> should have them login to their user account.
>
> I've not found the need to invoke sudo, su, or sudo su.
Running journalctl as regular user works, but only shows you the
messages from that user's session. It doesn't show you the full system
journal.
Maybe if you're in group wheel it shows you everything (?)
I'm in the habit of using sudo with it, but tried it..
[chris@flap ~]$ journalctl -b > nosudo.txt
[chris@flap ~]$ sudo journalctl -b > withsudo.txt
[chris@flap ~]$ diff nosudo.txt withsudo.txt
1c1
< -- Logs begin at Mon 2019-12-09 21:27:41 MST, end at Wed 2019-12-11
14:37:41 MST. --
---
-- Logs begin at Mon 2019-12-09 21:27:41 MST, end at Wed 2019-12-11
14:45:12 MST. --
3470a3471,3474
Dec 11 14:45:12 flap.local systemd[1357]: Starting Tracker metadata
database store and lookup manager...
Dec 11 14:45:12 flap.local systemd[1357]: Started Tracker metadata database store and
lookup manager.
Dec 11 14:45:12 flap.local systemd[1357]: Starting Tracker metadata extractor...
Dec 11 14:45:12 flap.local systemd[1357]: Started Tracker metadata extractor.
*shrug*
--
Chris Murphy