| helmut | hi. I based on discussion on debian-devel (https://lists.debian.org/debian-devel/2013/05/msg01453.html) I would like to ask you, supporting some of the interfaces of systemd in upstart would make sense. | 06:46 |
|---|---|---|
| helmut | specifically upstart and systemd use different mechanisms for socket activation and daemon completion signalling. at least the former needs explicit support from the daemon. | 06:47 |
| helmut | consolidating these interfaces would remove a lot of work (on the side of daemon implementations), and I guess that even though systemd came late to the party, upstart could adopting some of systemd's interfaces. | 06:49 |
| helmut | not because systemd's interfaces are better, but because consolidated interfaces are a benefit in themselves (and systemd devs are notoriously hard to work with when it comes to interoperability) | 06:50 |
| Neozonz|Disc | i've setup a script to launch a daemon | 08:03 |
| Neozonz|Disc | but after start daemonname | 08:03 |
| Neozonz|Disc | it just hangs | 08:03 |
| === Md__ is now known as Md | ||
| SpamapS | Neozonz|Disc: hard to respond without seeing the job file. | 15:24 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!