[systemd-devel] systemd logging isl broken

Michal Schmidt mschmidt at redhat.com
Fri Nov 11 07:18:36 PST 2011


On 11/10/2011 05:47 PM, Michael D. Berger wrote:
> This may be related to the problem repotred in
>    p4p1 changed to p2p1; works oddly
> reported on:
>    users at lists.fedoraproject.org

I don't see how network device naming is related to this.

>    /bin/systemctl enable myDaemon.service
>    ln -s '/etc/systemd/system/myDaemon.service'
> '/etc/systemd/system/multi-user.target.wants/myDaemon.service'
>    Failed to issue method call: Did not receive a reply. Possible causes
> include: the remote application did not send a reply, the message bus
> security policy blocked the reply, the reply timeout expired, or the network
> connection was broken.

Does "systemctl" without parameters report an error too?
Is it reproducible always?

Michal


More information about the systemd-devel mailing list