[09:54] <twiinz> hi there
[09:56] <twiinz> i'm planning to use upstart instances to manage subprocesses, i get the instance name from a database, im not sure what woud be the best approach to get all thoses instance to start automatically on a reboot, or on command
[09:58] <twiinz> so far i've worked out a system where my instances start on an event, and made second upstart conf file whose job is to loop throughout the list it got from the database and emits events
[10:00] <twiinz> but i've got a feeling there's an easier way to accomplish that, most of the examples i found about instance mention ttys, is there a built in way to say in the instance conf file, for the given runlevels iterate through this list of ttys [1, 2, 3, 4, 5, 6]?
[18:27] <BleSS> does upstart is only valid to use with shell scripts?
[18:28] <ion> Upstart can run and monitor any processes.
[18:28] <BleSS> I say because I'm changing my bash scripts to python since that bash is very cryptic and unmaintaneable
[18:31] <BleSS> ion: but in the next page http://upstart.ubuntu.com/getting-started.html says: shell script code that will be executed using /bin/sh
[18:31] <ion> The job definitions support scripting in sh, yes.
[18:32] <BleSS> so it isn't possible use python there, is it?
[18:35] <ion> Within job definitions? Not at the moment at least. But job definitions tend to be so simple sh is sufficient. Having a single interpreter for all job definitions is a good idea IMO, unless there’s a compelling reason to change that.
[18:42] <BleSS> thanks ion