[08:00] <hitlin37> hi
[08:00] <hitlin37> i havce a job which chehcks in pre-start for configuration.
[08:01] <hitlin37> and then it starts on as  : start on started main_engine
[08:01] <hitlin37> now main_engine sometimes gets killed and respwan. that makes my job to skip pre-start
[08:02] <hitlin37> how to make a job to alwayys chehck pre-start
[11:26] <hitlin37> Hi, would could be the reason when you reasnpn a message
[11:26]  * hitlin37 killed by TERM signal
[11:26] <hitlin37>  killed by TERM signal
[15:11] <kline> hi, whats the best way to start an upstart job after one sysv service (postgres) but before another (server application). im under the impression that upstart itself for sysv services only emits per-run level events
[15:12] <kline> really i want to do some database maintenance after postgres has started but before the application server starts
[15:15] <hitlin37> kline: i use the cookbook for the help
[15:15] <hitlin37> that's the only thing available.
[15:15] <kline> hitlin37: i couldnt see anything clear in that
[15:15] <kline> but thanks for the suggestion
[15:24] <kline> for changing sysv scripts to upstart, is it as easy as wrapping them in script/end script and prepending their metadata?
[15:31] <hitlin37> no idea on that
[15:31] <hitlin37> i'm new to upstart as well
[15:31] <hitlin37> how many suchscripts you have?
[15:31] <hitlin37> if its not too many, may be you can re-wrtie
[15:35] <kline> i have two scripts (postgres and appserver), but i dont understand them well enough to rewrite from scratch
[15:36] <kline> i know systemd far better than sysv and upstart, but at work we use ubuntu for some of our servers, including this one
[15:36] <kline> (testing machine that needs the database wiped and repopulated on reboot, hence the task im trying to insert)