Thanks for your question, but, thinking my system was seriously damaged for a number of reasons, I have blown it away and installed F16_64. It has its own problems, but so far I have not done anything with systemd. I will soon. I was happy to see many fewer files in /etc/init.d/ . Not that I don't like sysV, but I found the mixture, shall we say, unaesthetic.
Mike. -- Michael D. Berger [email protected] http://www.rosemike.net/ > -----Original Message----- > From: > [email protected] > g > [mailto:[email protected] > sktop.org] On Behalf Of Michal Schmidt > Sent: Friday, November 11, 2011 10:19 > To: [email protected] > Subject: Re: [systemd-devel] systemd logging isl broken > > 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: > > [email protected] > > 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 > _______________________________________________ > systemd-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > __________ NOD32 6621 (20111111) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > > _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
