Hi Leo, On 03/17/2014 03:20 PM, Leo Baltus wrote: > Hi, > > I am trying to get opendnssec squeezed in our environment. Our > management system requires that multiple instances can be run from > the same software. > > Usually this boils down to starting a service with a single > command-line option pointing at the right configuration file. The > configuration then points to locations where each instance can have > its own resources like pidfiles, data, logfile, etc. > > With opendnssec however it seems that at least the location for the > pidfile and command-socket in signerd takes a default from configure > --localstatedir-option but it seems it is not configurable during > runtime through a command-line configuration option or environment > variable. Am I overlooking something?
You are not overlooking something. Such configuration options do not yet exist. I agree and think we should implement that. > Also when starting signerd with 'ods-signer start' I can't give an > option to point at conf.xml My workaround is to start ods- signerd > directly like ods-enforcerd. Is this a supported way of starting > signerd? ods-signer indeed has not such an option, but starting the signer daemon directly with ods-signerd is indeed a supported way of starting the signer engine. Best regards, Matthijs _______________________________________________ Opendnssec-user mailing list [email protected] https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
