[Opendnssec-develop] socket for command and control?

[Matthijs Mekking]

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

Hi,

The signer engine already works with a such a control interface:
ods-signer. I think you can copy most of the code, though I do include
my internal logging and malloc header files. The client side is
implemented in signer/src/ods-signer.c. The server side is covered by
signer/src/daemon/cmdhandler.{c,h}. The latter does depend on some more
signer engine specific code, but merely to be able to execute the
commands, rather than handling them.

I think it would be good to keep the pidfiles, but don't rely on them
for starting and stopping services.

Best regards,

Matthijs

On 08/23/2010 02:11 PM, Sion Lloyd wrote:
>> how much work would it take to add a socket command and control interface
>> to the enforcer and the signer engine? it would be good if we could get
>> rid of the pid-files for version 1.2.
> 
> I've never written code for this, but from a position of no experience it 
> doesn't seem like it should be too hard...
> 
> Matthijs: have you ever done this in c? I guess that we only need one of us to 
> write it and add it to the common code?
> 
> Sion
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMc4pXAAoJEA8yVCPsQCW5FuAIAMGWCNyms59RWdsRQxK/Bbul
QOCMCme9aB1SlHX4lAyRI7SLdxW8Tm9+eEjuwtuVS7EGxjeoLiaupKq/qgVO0yvo
Bfa7TA8pKxENUfXoPJ0XrcQPy7whMrXbnkrUNMF7LdsSmhQoCw8BSAgzoIWmGR8W
tO8jJbrhWjdC9ANBqdCYCEbxhCxwHI/L2caCUJ9kNGEO2rpALssw0V7XqoFCAC9w
R+G3hOrCd8ynmHptzRSqfc2UKGDCS+cjSkJcrkWrbJmwu18DVG9TJLdt5+7MtkYN
zqhbWmZH7w0oLsW41lmBmwk511F8Xwd0pzgXweT76oBheis912jlLIuiTLj0T7A=
=XFAd
-----END PGP SIGNATURE-----