I have all of my upstart config files under version control. My ideal way to use upstart is to create soft links from my version control repository (mercurial - not that it matters) into /etc/init but upstart fails to see the jobs. Everything is fine if I copy the files from the repository directory to /etc/init.

Anyone know why upstart fails to handle symbolic or even hard links?

Thanks

Chris

link|improve this question

67% accept rate
1  
Perhaps it was a design decision on the part of the Upstart developers to ignore soft links? Anyway, if your repository is on the same partition as /etc/init, try using hard links. – Steven Monday Oct 20 '10 at 18:06
Tried hard links and that didn't work either :-( – Chris McCauley Oct 20 '10 at 18:25
feedback

1 Answer

up vote 7 down vote accepted

Upstart watches its configuration directories with inotify and reloads the configuration when any of the files change or a new file is added. Apparently this doesn't work for symlinks.

To manually update the configuration use

$ initctl reload-configuration
link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.