[12:17] <lexflex> hi!
[12:21] <lexflex> question: is upstart not used/activated/installed with a fresh debian 7 install?
[13:51] <Screwba> anyone around?
[13:52] <Screwba> Have a question on UpStart boot up pausing
[13:53] <Screwba> I want to run a script a single time upon boot up which will make some configuration changes to the system.  I have tried creating an UpStart Event but this seems to run and everything else runs with it, it does not pause the boot sequence and wait to finish until the rest of the boot up happens
[13:53] <Screwba> is there a way I can accomplish this easily?
[13:54] <Screwba> I have also tried running through rc.local within a loop watching the script but it still does not complete.  I really want the script to run once I have an IP address
[14:34] <Screwba> ping
[14:56] <xnox> lexflex: sysvinit is default in fresh debian 7 install, you can install upstart package & reboot and use upstart =)
[14:57] <xnox> Screwba: read cookbook, there is a way to "block" other jobs from executing. You mostly likely want your job to start at network-interface IFACE!=lo and before runlevel job is executed.
[14:58] <xnox> Screwba: alternatively you can use an override, e.g. echo "start on started your-magic-job" > /etc/init/runlevel.override, to prevent runlevel 2 event emitted before your job is executed.
[14:59] <xnox> Screwba: i'd recommend to use initctl2dot to generate a graph of all jobs/events on your machine, for you to clearly see & decide where to plug your job in.
[14:59] <lexflex> xnox: but i read in various places "only do this when you know what you're doing" which i dont :)
[15:00] <xnox> Screwba: also maybe look at cloud-init, it's a few upstart jobs that modify system configuration on boot. That's what is used by most cloud providers to modify "stock" image into a "unique" cloud instance.
[15:01] <xnox> lexflex: we are here to help. it does work great, but there can be debian specific bugs/quirks. You will be able to revert back easily by installing sysvinit again.
[15:01] <xnox> lexflex: do think why you want to do this and whether you have time to troubleshoot if something goes wrong.
[15:14] <lexflex> xnox: I'm trying to set up uwsgi and django
[15:15] <xnox> lexflex: debian has eloquent uwsgi init scripts which let you configure a "projects" and it will start them all individually. Not sure if upstart will gain you anything, just for that.
[15:42] <Screwba> xnox: THANKS A LOT...I went through the cookbook and nothing really poked out at me but this guidance is JUST what I need.
[15:42] <lexflex> xnox: the thing is i couldn't find them
[15:42] <lexflex> i didn't use apt-get
[15:43] <xnox> lexflex: apt-cache search uwsgi
[15:43] <xnox> lexflex: apt-cache search django
[15:46] <lexflex> xnox: in the uwsgi doc it said the packages are outdated and i should build from source or something
[15:46] <lexflex> i _think_ thats what i did
[15:46] <lexflex> but now there are no init.d scripts or anything, just a bin
[15:49] <xnox> lexflex: stable/testing has 1.2.3, unstable has 1.9.13, latest upstream is 1.9.14.
[15:49] <xnox> lexflex: if you don't know how to use/compile software from source. It's best for you to use the package from debian, it's properly compiled & easy to use out of the box.
[15:49] <xnox> lexflex: and has proper init.d scripts & simply just works on debian.
[15:50] <xnox> lexflex: does it actually matter to you if you are using 1.2.3 or 1.9.x? are there features you rely on from newer uwsgi? as far as I can tell django would work with either.
[15:50] <lexflex> xnox: is unstable obtainable by apt-get?
[15:56] <Screwba> xnox:  cloud-init is not in the cookbook, should it be?  doing a search online for it now
[15:57] <xnox> Screwba: cloud-init is an upstrem project and a package in ubuntu. Google for cloud-init, or ubuntu cloud images. Or blog posts by smoser / hallyn. 
[15:59] <xnox> Screwba: the cookbook is about upstart and  best practises in writting upstart jobs. cloud-init has leveraged upstart jobs, but it does a lot more than just upstart jobs. it can configure your system, install/upgrade packages, resize filesystems, etc....
[16:02] <Screwba> xnox: found it and have read the doc on it...seems pretty cool.  I will see if I am going to use that or use the Blocking method in the cookbook...thanks again, your info is definately valuable.   =)
[16:17] <lexflex> xnox: I guess not. I'm a Linux/Python/Django noob, so :)
[16:18] <lexflex> xnox: but the uwsgi docs say "Suggestion: when you start learning uWSGI try to build from official sources, using distro-supplied packages could bring you lot of headaches. "
[16:19] <lexflex> xnox: and also: "If you think about writing some init.d script for spawning uWSGI, just sit down and realize that we are no more in 1995."
[16:22] <xnox> lexflex: this is not a support channel for uwsgi/django. try #ubuntu for general support.
[16:22] <xnox> lexflex: or uwsgi/django forums.
[16:27] <lexflex> xnox: I know, but you asked me why I wanted to use upstart. and the reason is simply that the uwsgi docs suggest it
[16:28] <lexflex> and also suggests compiling the source, which results in not having init.d. that's how I went trying using upstart
[16:29] <xnox> lexflex: sure, it also suggests other systems as well. it makes sense to use upstart jobs for self-compiled uwsgi, if you already have system running under upstart =) there are other ways as well.
[16:29] <lexflex> xenox: so a upstart related question: what happens when i install upstart and disable the "standard" under debian? will init.d be ignored from that moment on?
[16:30] <xnox> lexflex: i do suggests you $ apt-get install uwsgi, drop a config file for it in /etc/uwsgi.d/ & start developing/running your django apps =)
[16:30] <lexflex> but i want to learn about upstart now that i heard of it :P
[16:30] <xnox> lexflex: upstart does support executing normal init.d scripts, so everything will continue to work.
[16:31] <lexflex> oh, okay. so it will execute the existing ones as well as the upstart ones?
[16:31] <lexflex> why isn't it standard then? why do i "have to know what i do" to replace it?
[16:57] <JanC> sysvinit has been the default for ages, upstart and a bunch of other init systems are available for those who want, but aren't the default because people couldn't agree (yet?) which one should be the default
[16:58] <JanC> but that's more a Debian question than an upstart one really...
[16:58] <lexflex> JanC: well upstart should be the default obviously!! ;)
[16:58] <lexflex> just kidding
[16:58] <JanC> it's the default in Ubuntu & Ubuntu derivatives
[16:59] <lexflex> oh, okay
[16:59] <lexflex> as a Windows veteran I have to wrap my mind around different "init systems"