[00:30] Can anyone share a link showing how to start multiple init services with another upstart service? [08:49] fedora_newb: What do you want to do, specifically? [08:59] AnrDaemon, so I have a couple of upstart services that handle laravel (php) stuff. Exec their own commands. I would like another upstart service that I could use to pass start/stop to control all the other services at once [09:00] brrr [09:00] What stops you from just creating relevant pools in PHP FPM? [16:52] AnrDaemon, never really thought about that. Hmm... [16:56] And specifically, what "laravel stuff" you are managing? F.e. what do you mean by "their own commands"? [17:08] AnrDaemon, most using their artisan command stuff to do jobs in the background, such as sending messages or processing other data that takes longer. We are currently using supervisor but the server is having trouble with it sometimes and randomly crashes. So I figured I would hop on upstart and give that a go. [17:09] Well, that's an entirely different question then. [17:09] I have the configurations for each job (sending messages, moving members around, etc) but I would like another upstart server (maybe task?) to start and stop all of them at once [17:09] service* [17:09] However, I usually get service not found (like the specific job itself) or it just stops [17:10] I think you just need a better supervisor for that. [17:10] Anything you can recommend? [17:10] Because you can't efficiently detect if a task finished successfully or crashed. [17:10] Nothing off the tp of my head, sorry :'( [17:13] np sir. I just read that upstart was similar to supervisor, so was giving it a try [17:14] Similar, yes, but it is very generalised and geared towards the daemon supervision. [17:15] Supervising finite running tasks… I'm not sure it is possible, but you may try. Just heed the warning: avoid using a script ... end script as your job as much as possible.