Ondřej Surý writes:
> networks, mounts are ok, but how you are going to make sure that a
> remote MySQL server is available from within a local init system?
>
> > Is it unreasonable for OpenDNSSEC to require certain resources to be
> > available before starting?
>
> With remote MySQL you
No, the init script name is not the issue here. I'll look into it though.
On 13 December 2016 17:34:19 Bas van den Dikkenberg wrote:
I also found a another issue the name of the init script is to long see:
root@myserver:~# /etc/init.d/opendnssec-enforcer restart
* Restarting OpenDNSSEC Enfo
On Tue, 13 Dec 2016, Ondřej Surý wrote:
E.g. instead of failing to start when MySQL is not available, it should
refuse to run the first operation in the queue until it is connected,
etc.
+1
Also, runtime linking support for mysql versus sql would be a great
improvement so packages don't need
I also found a another issue the name of the init script is to long see:
root@myserver:~# /etc/init.d/opendnssec-enforcer restart
* Restarting OpenDNSSEC Enforcer opendnssec-enforcer
On Mon, Dec 12, 2016, at 21:08, Yuri Schaeffer wrote:
> Hi Ondřej,
>
> > this has to be solved in OpenDNSSEC itself.
>
> Forgive me my ignorance but I always thought making sure mounts,
> network, services or other dependencies are available is _exactly_ the
> problem init systems are supposed to