On 03/02/2013 04:31 PM, Ed Greshko wrote:
On 03/03/13 08:22, Joe Zeff wrote:
> On 03/02/2013 03:45 PM, Ed Greshko wrote:
>> man journalctl
>
> Thanx; that hadn't occurred to me. Checking, I find that it depends on
syslog.socket.service, which also failed. I'll start a new thread for that because I
don't think it's related to the OP's question.
Also, just to be clear, it isn't.
"systemctl status journalctl.service"
it is
"systemctl status systemd-journald.service"
That one's running OK. Still, I'm curious about why the other one's
there and failing.