[Opendnssec-user] socket and pid-file location

Leo Baltus Leo.Baltus at omroep.nl
Mon Mar 17 15:40:23 UTC 2014


Op 17/03/2014 om 16:24:46 +0100, schreef Matthijs Mekking:
> 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.

Ah, okay. If you have any patches I would gladly test them.

-- 
Leo Baltus, internetbeheerder
NPO ICT Internet Services
Bart de Graaffweg 2, 1217 ZL Hilversum
servicedesk at omroep.nl, 035-6773555



More information about the Opendnssec-user mailing list