Re: [systemd-devel] Starting units when a port is available for connections

2015-06-18 Thread Lennart Poettering
On Thu, 28.05.15 18:35, Adam Zegelin (a...@instaclustr.com) wrote: > > > On 27 May 2015, at 8:40 pm, Andrei Borzenkov wrote: > > > > Hmm ... this sounds suspiciously like what D-Bus does. Did you consider > > using D-Bus in your application? > > > > But for now there is no way to express such

Re: [systemd-devel] Starting units when a port is available for connections

2015-06-18 Thread Lennart Poettering
On Wed, 27.05.15 19:09, Adam Zegelin (a...@instaclustr.com) wrote: Heya, > I’ve successfully managed to set the service type to “notify” and > modify C* to call sd_notify() when is ready to accept client > connections. Further experimentation reveals that this is not an > ideal solution. C* can

Re: [systemd-devel] Starting units when a port is available for connections

2015-05-28 Thread Adam Zegelin
> On 27 May 2015, at 8:40 pm, Andrei Borzenkov wrote: > > Hmm ... this sounds suspiciously like what D-Bus does. Did you consider > using D-Bus in your application? > > But for now there is no way to express such dependency in systemd; > D-Bus being exception, you can make services dependent o

Re: [systemd-devel] Starting units when a port is available for connections

2015-05-27 Thread Andrei Borzenkov
В Wed, 27 May 2015 19:09:57 +1000 Adam Zegelin пишет: > Hi list, > > I’m running Cassandra (C*, a clustered database) as a systemd service. > Currently this is just a “Type=simple” service, as such, dependant units will > start as soon as the C* process starts rather than when C* is accepting

[systemd-devel] Starting units when a port is available for connections

2015-05-27 Thread Adam Zegelin
Hi list, I’m running Cassandra (C*, a clustered database) as a systemd service. Currently this is just a “Type=simple” service, as such, dependant units will start as soon as the C* process starts rather than when C* is accepting client connections. I’d like to transition to something more com