[Opendnssec-develop] A NotifyCommand script blocks, what to do?

Matthijs Mekking matthijs at NLnetLabs.nl
Wed Oct 19 13:00:15 UTC 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is a follow-up from today's meeting AOB.

The case:
OpenDNSSEC has a <NotifyCommand> configured to notify a name server.
The configured script never terminates and the associated worker and
zone are being blocked and will be forever in the [write] task.

Is this what we want (let the worker wait until the notify command is
terminated)? Or do we want the signer daemon to fork off the notify
command script and continue its process regardless of the result of the
notify command script? In the latter case, you will get fresh signed
zone files, but we don't know if they are ever picked up by the name server.

Best regards,
  Matthijs

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOnsnfAAoJEA8yVCPsQCW5NhkIAM80gMgHKFCQv/DIajc/iZ5B
hoRoU8DfQD7cbtRKy3GFyPCrOFTQJ7/GWDTIEvqivSsq8GoUxEwfbm1tBNl/YuA6
xNUJpxuzr2QF3okfqG8VmB/WIQ4hkSuJPCpPQelSIvtZ1Je9GeNv7bl5CRD/mgrv
A0yEfziszyK+gcM6GGfhzDFW/+aT/CtZIh/O8scU8pNvAL4o+hxC9PVGoH13qzAd
wmTLyslxj+L526IzZgiLuH//mxpLvh4/NdZanh7WsJZ6+B+NNqjRzQZInXzTKMY7
UDLlhpufxShY1EYNvFnlGOiLEQ8HMwp3LDNb8CZl6IXR2CLEMMGkwiRBnBS/R64=
=DdhV
-----END PGP SIGNATURE-----



More information about the Opendnssec-develop mailing list