[bind10-dev] Storing files by dhcp components
Tomek Mrugalski
tomasz at isc.org
Tue Jan 8 15:45:30 UTC 2013
On 08.01.2013 13:54, Shane Kerr wrote:
> Michal,
>
> On Tuesday, 2013-01-08 12:14:45 +0100, Michal 'vorner' Vaner
> <michal.vaner at nic.cz> wrote:
>> Hello
>>
>> On Tue, Jan 08, 2013 at 11:09:38AM +0100, Shane Kerr wrote:
>>> You may want to use the same technique as the b10-cfgmgr for
>>> this, which is to take a command-line argument pointing to the
>>> correct directory, which the boss process sets when invoking
>>> the program.
>>>
>>> Have a look at src/bin/bind10/bind10_src.py.in to see how the
>>> boss starts this, and src/bin/cfgmgr/b10-cfgmgr.py.in to see
>>> the b10-cfgmgr implementation.
>>
>> The config manager is special-cased in boss. I don't like the
>> idea of special-casing anything more (actually, I'd like to stop
>> special-casing auth and resolver). So, to pass that information,
>> I believe we need some other mechanism, possibly over the msgq.
>
> Whoops, good point. A much more reasonable idea is to simply make
> this a configuration parameter. *blush*
I'm not sure if it is optimal solution, but I'll play along. Any
recommendations for default value for that parameter?
The problem I have with exposing this to user configuration is that if
the user changes the directory, suddenly server will loose its server
identifier after next restart. This would in turn cause server to
reject existing clients' requests (because of server-id mismatch). But
that problem can be solved by writing existing server-id to the new
directory if it changes.
Tomek
More information about the bind10-dev
mailing list