I have a django app that i am looking to deploy. I would like to use upstart to run the app.
I have mysql installed (from repos) on a development machine (laptop) and I don't need the daemon running on every boot. I've copied /etc/init/mysql.conf to /etc/init/mysql.conf.old and then removed everything following the "start on" line.
Upstart is installed, but init-checkconf is not. Any ideas how to get both?
$ sudo init-checkconf
sudo: init-checkconf: command not found
$ sudo dpkg --get-selections | grep upstart
upstart install
$ uname -a
Linux VM1 2.6.32-38-server #83-Ubuntu SMP Wed Jan 4 11:26:59 UTC 2012 x86_64 GNU/Linux
As I asked in the title, I'm looking for a script/command to find the correct directory (usually /etc/init.d or /etc/rc.d/init.d).
Right now I'm using
dirname `find / -name acpid 2> /dev/null | grep /etc/`
but sometimes I get more than one result (probably some of the results are link) . Any suggestion?
One thing that always confused me in Ubuntu was how system services are started. I know that Ubuntu uses Upstart and supports SysV, but which one is used to start the services?
I need to re-order init scripts, particularly so that some of my own will run before certain others. What documentation should I be looking at for thorough information on how that is done (aside from the effects of the changes).
This is in a cloud environment using the cloud-images tree, with cloud-init in the mix.
I want to replicate the Heroku Git build process on my server using gitolite, a post-receive hook and foreman.
The pushed repository has a Procfile in it, so I can generate the upstart scripts using foreman like so:
foreman export upstart /etc/init
Everything works as expected, the app builds on push, but the git user running the export has no sudo privileges, and therefore cannot write the ge
man init, (and init(5) initctl(8) telinit(8) runlevel(7) startup(7) starting(7) started(7) stopping(7) stopped(7)) hold more info, but some good examples may be helpful in understanding all this. [by r_hartman]
during the upgrade process I was wondered for "replace init.d", and I said "keep", not replace. Now, apache2 is not working. I tried removing and upgrading again, but doesnt start.
I have this error message:
sudo /etc/init.d/cron start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g.