=== Md is now known as Guest78494 === Guest78494 is now known as Md [09:54] hi there [09:56] 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] 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] 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]? === robbiew_ is now known as robbiew [18:27] does upstart is only valid to use with shell scripts? [18:28] Upstart can run and monitor any processes. [18:28] I say because I'm changing my bash scripts to python since that bash is very cryptic and unmaintaneable [18:31] 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] The job definitions support scripting in sh, yes. [18:32] so it isn't possible use python there, is it? [18:35] 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] thanks ion === robbiew is now known as robbiew_