Hi,

Thomas Hood wrote:
> I am referring to /etc/resolvconf/update.d/pdns, not to
> /etc/init.d/pdns-recursor.
> 
> No, I didn't try the script.  Having extra directories in
> PATH doesn't break anything; it's just a bit unclean.
> 
Ok, my fault, I corrected that in my svn version.

> 
> 
>>Hm, ok, isn't it better to put it in /var/run/powerdns ?
> 
> /var/run/powerdns/ is preferable IF it can be used.  /var/run/
> can be safely used iff the file to be stored there does not have
> to be accessed before network drives are mounted at
> /etc/rcS.d/S45mountnfs.sh.  (Reason: Debian supports putting /var
> on a network drive.)
> 
> The problem is that resolvconf initializes before networking
> (for obvious reasons) at /etc/rcS.d/S38resolvconf; the latter
> script runs the resolvconf update scripts.  Resolvconf update
> scripts can get run again as a result of ifups done in
> /etc/rcS.d/S40networking and other places.
> 
> So /var/run/powerdns/ can be used provided:
> 
> 1. /etc/resolvconf/update.d/pdns is modified so that it doesn't
>    do anything if /var/run/powerdns is absent;
> 2. and something ensures that /etc/resolvconf/update.d/pdns gets
>    run after /etc/rcS.d/S45mountnfs.sh and before pdns starts
> 
> #1 is easy to implement:
> 
>     [ -d /var/run/powerdns ] || exit 0
> 
> #2 can be implemented (a bit hackishly) by including a call to
> /etc/resolvconf/update.d/pdns in the pdns initscript.
> 
> I hope I have said enough to explain the issues involved.

I understand fully the issues you explained. But I have one concern
about it. I violate the FHS (2.1, 2.2 and 2.3 of the FHS) if I add a
/run directory. That's why I asked for /var/run/powerdns. What are your
thoughts about that ?

Don't see it wrong that I don't want to follow your suggestion. But
/var/run/powerdns is in my eyes the best option we have. The first one
is idd easy to implement. The second one is I think also easy, I only
need to add a call at start of pdns.

I think I go for /var/run/powerdns and implement the 2 points.

Regards,

Matthijs Mohlmann

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to