On Wed, 16.03.11 16:34, Jerry James (loganjerry@xxxxxxxxx) wrote: > > On Wed, Mar 16, 2011 at 4:25 PM, Lennart Poettering > <mzerqung@xxxxxxxxxxx> wrote: > > On Wed, 16.03.11 12:29, Jerry James (loganjerry@xxxxxxxxx) wrote: > > > >> For the last few days, I've been getting email from anacron after > >> cron.daily runs on my F-15 box. The body of the email is: > >> > >> ------------------------------------------------------------------------------ > >> /etc/cron.daily/prelink: > >> > >> Couldn't find an alternative telinit implementation to spawn. > >> ------------------------------------------------------------------------------ > >> > >> I did a web search on that phrase. It looks like this is systemd > >> deciding that it is not in charge, attempting to forward some request > >> to upstart, and failing to exec /lib/upstart/telinit. I don't see > >> anything related to this in /var/log/prelink/prelink.log. Is prelink > >> somehow causing systemd to execute? > > > > Hmm? I am not sure I follow, but F15 is systemd, not Upstart. > > Yes, I know that. Let me try again. I am receiving the email quoted > above. What I really want to know is what is triggering the condition > that causes this email to be sent. I only mentioned upstart because > the code in systemd that generates the error message does so when it > tries to forward a request on to upstart, but fails to exec > /lib/upstart/telinit. Upstart is not otherwise germane to the issue. Hmm, we don't forward to Upstart unless systemd is not running. To check whether systemd is running we look whether /sys/fs/cgroup/systemd is a mount point. If taht fails in your case something is really wrong. What does the following line print? systemd-notify --booted ; echo $? Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
