On Mon, Jun 29, 2015 at 9:30 AM, Timothy Murphy <gayle...@eircom.net> wrote: > > > I tried "sudo journalctl _SYSTEMD_UNIT=rngd" > but just got the response >
This doesn't answer your *real* question, but here's how I did the culling: # journalctl -u rngd -b 1 > Logs begin at Tue 2015-01-13 07:42:13 CET, >> >> [root@snowcrash bin]# journalctl -u rngd -b 1 > > -- Logs begin at Tue 2013-10-15 14:15:34 MDT, end at Mon 2015-06-29 >> 10:09:59 MDT. -- > > Oct 15 15:57:25 snowcrash systemd[1]: Starting Hardware RNG Entropy >> Gatherer Daemon... > > Oct 15 15:57:25 snowcrash systemd[1]: Started Hardware RNG Entropy >> Gatherer Daemon. > > Oct 15 15:57:31 snowcrash systemd[1]: Starting Hardware RNG Entropy >> Gatherer Daemon... > > Oct 15 15:57:31 snowcrash systemd[1]: Started Hardware RNG Entropy >> Gatherer Daemon. > > Oct 15 15:57:31 snowcrash systemd[1]: rngd.service: main process exited, >> code=exited, status=1/FAILURE > > Oct 15 15:57:31 snowcrash systemd[1]: Unit rngd.service entered failed >> state. > > > end at Mon 2015-06-29 17:25:30 CEST > "-b 1" means only show logs from the most recent boot, and "-u rngd" means show only logs from the "rngd" unit. I presume I haven't got a hardware entropy device either so the daemon just exits. The real question is why it doesn't work that way for you. I did figure this out from reading the journalctl man page, so maybe I am a machine too :-) --Greg
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
