Can upstart handle symbolic links to config files

ubuntu-10.04upstart

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

Best Answer

Upstart does not support symlinks because they might point to a file on a partition that is not loaded at boot time.

I have gotten around this in my own project by putting the conf files in /etc/init/myscripts and then binding that to a directory in my repository. mount --bind /etc/init/myscripts ~/code/repo/initscripts.

Add this to /etc/fstab and the binding will be persistent:

/etc/init/myscripts  /home/me/code/repo/initscripts      none    bind

This effectively gives you hard-linked directories. Upstart will treat the conf files as any other, because they are local to /etc/init. Your DVCS will also see them as local files in the repo, so it will also treat them as it would any other files stored there. Best of both worlds.

Related Solutions

Ubuntu – How to start nginx via upstart

You cannot have multiple stop on directives in an upstart job description for Upstart >= 0.5.

And console owner is probably not what you want (this makes nginx the owner of the system console).

Try:

description "nginx http daemon"
start on runlevel 2
stop on runlevel [016]
console output
exec /usr/sbin/nginx -c /etc/nginx/nginx.conf  -g "daemon off;"
respawn

Upstart config to start sync daemon as non-root user

sudo by default stomps on most of the environment. Try this (adding -E):

exec sudo -E -u rsyncuser -c "ls -la" >> /tmp/upstart.log 2>&1

-E tells sudo to preserve the environment.

Best Answer

Related Solutions

Ubuntu – How to start nginx via upstart

Upstart config to start sync daemon as non-root user

Related Topic