[01:03] <jefimenko> hello
[01:03] <jefimenko> i'm trying to setup upstart for a custom service
[01:04] <jefimenko> i already have a legacy sysv initscript for this service and my main goal is to have the service respawned if it crashes etc.
[01:04] <jefimenko> but i'm finding the docs on upstart light and not that many people seem to be using it yet
[01:04] <jefimenko> it seems great though
[01:04] <jefimenko> i'm on ubuntu-server, btw
[01:16] <jefimenko> could anyone give me a little guidance on this?
[05:57] <freshtonic> Is it possible to have an upstart service start and supervise a group of processes as a single logical service?  i.e. I want an instance of a process to run for each CPU core on my system, and if one crashes it must be restarted.
[05:58] <freshtonic> I suspect that it doesn't support this usecase and I'll need to write some master process that is managed by upstart and master process manages the group of worker processes.
[05:58] <freshtonic> But it would be good to be wrong :)
[06:04] <jefimenko> i'm trying to write a jobfile and would like to do sanity checks in the pre-start script
[06:04] <jefimenko> if any of these checks fail i would like to log debug information somehow
[06:04] <jefimenko> with sysv initscripts i used to just use echo or something
[06:04] <jefimenko> is there a way to do this in upstart?
[07:25] <jefimenko> anyone awake?
[09:15] <tstone> which is the most simplest shutdown config. I've looked at the ubutuntu 10.4 stuff but it used runlevels. I'd like to use s.t. without any runlevels.
[14:08] <tstone> hi, im still working on the ptxdist integration for upstart. Right now i confused which might be the simplest shutdown system, without any runlevel support?
[14:24] <Keybuk> tstone: however you like, I guess
[14:30] <tstone> mh, is there a way to wait for all "managed" processes to be stopped
[14:31] <tstone> more precicely without knowing which processes are all configured/running
[14:38] <tstone> or put the other way: is there an event if everything is stopped, otherwise i would need a dependency for every package installed, without knowing which packages will be installed, no?
[14:40] <Keybuk> I'm not sure I follow you, sorry
[14:42] <tstone> have to leave right now... thanks for listening
[14:56] <ion> tstone: With Upstart 0.10, there will probably be a job called “system” or something like that. It will have a shutdown command in postinst and other jobs will have something like “while system”, so they’ll be stopped just before the shutdown command is run. You can do something similar, although not as nice, with current Upstart: do the same thing (and add “start on startup” to the system job), but since we don’t have “while”, use something like ...
[14:56] <ion> ... “start on started system, stop on stopping system” in jobs that only depend on that (and not e.g. filesystem).
[15:01] <Keybuk> pretty much exactly like that, yeah