Upstart has gained the ability to start a process after a socket is accessed, but I found the feature to be poorly documented. How is a socket-activated daemon and upstart config written?
I ran into an issue where I needed my upstart script to wait for the libvirt-bin socket, as you can't just used
Anyway, I ended up making my upstart script like so:
Per the documentation referenced by @sr_: