How do I verify whether upstart is the problem

Asked by Tommy Trussell on 2008-05-29

I opened Bug #176472 back in December and I suspect that it is an upstart issue, but I don't understand how upstart works well enough to know how to test it. I have looked through the upstart bugs but didn't see anything similar to it. So if it IS an upstart issue, I presume it's unique.

Basically netatalk doesn't start on boot, but starts when invoked manually. Would the best test for this be to install sysvinit and see if it works then, or is there a debug procedure in upstart? I have determined that the /etc/init.d/netatalk script is NOT being called on boot (lines I added do not appear on the console or anywhere), but I don't know what to try next.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu upstart Edit question
Assignee:
No assignee Edit question
Solved by:
Tommy Trussell
Solved:
2008-05-29
Last query:
2008-05-29
Last reply:

In the process of composing my question, I thought to try installing sysvinit, which replaced upstart. Yes, netatalk started by itself using sysvinit. This is on an Ubuntu Gutsy 7.10 system. I'll update the bug, and if it's wrong to point the blame at upstart I am sure someone will let me know.

I'm assuming this proves it's an upstart issue so I'm closing this question.