On Thu, Mar 29, 2012 at 9:34 PM, David Jeske <[email protected]> wrote:
> On Thu, Mar 29, 2012 at 6:20 PM, David Jeske <[email protected]> wrote: > >> 1) I'm having trouble where I edit my /etc/init/myprog.conf file, initctl >> reload-config, then initctl restart myprog, and my config changes are >> obviously not being used.. >> > > shortly after sending this, I realized what might be related... I'm > sym-linking from my /etc/init/willow-smtpd.conf -> > /home/willow/.....(actual file under source control) > > The man-page says upstart uses inotify, so I figured it wouldn't see my > edits without my manual reload. > > However, even with my manual reload it didn't see my changes.. like it's > checking the mod-date (in this case of the symlink) and being > too-smart-for-its-own-good and not reloading the file. > > copying the "regular file" into /etc/init instead of using the symlink > made my problem go away. > > Is there some reason that symlinking into there is an intentionally > unsupported behavior? > Yes, symlinks are intentionally unsupported. See [1]. If they live on the same filesystem, you can still use a hardlink for testing. Cheers, Evan [1] http://upstart.ubuntu.com/cookbook/#symbolic-links-don-t-work-in-etc-init
-- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
