[15:38] <AnrDaemon> l2y: initctl show-config <servicename>
[15:39] <AnrDaemon> l2y: "start on" inidicates that the service was set to autostart.
[15:39] <l2y> AnrDaemon: yeah, eventually found it in the upstart cookbook, but thanks
[15:39] <l2y> for some reason, google didn't help
[15:39] <AnrDaemon> :)
[15:40] <l2y> I guess because I'm using imprecise terminology
[15:40] <AnrDaemon> Google has hard times to search for too generic terms.
[15:41] <AnrDaemon> But cookbook is a source of information. Even though it's not always clear.
[15:41] <l2y> because systemd clearly has `enabled` state, what `enabled` means to upstart is unknown, it can be described as `can start at boot` but not with one word
[15:41] <AnrDaemon> Some relations are not directly obvious.
[15:41] <AnrDaemon> systemd is modelled differently.
[15:42] <AnrDaemon> There are similarities between the two, but the one major diverging point is dependencies. In upstart, all dependencies are explicit. Which is kind of a roadblock for big distributions.
[15:43] <AnrDaemon> I.e., in upstart, you can't say "start this job after that one, if it's installed, otherwise, just start it, I don't care".