[pkg-dhcp-devel] Bug#860928: dnssec-trigger + isc-dhcp-client: /etc/ being cluttered with tons of resolv.conf.dhclient-new.* files

Roberto C. Sánchez roberto at debian.org
Fri Oct 27 14:37:55 UTC 2017

On Sat, Apr 22, 2017 at 02:26:59AM +0200, Axel Beckert wrote:
> * dhclient remove /etc/resolv.conf.dhclient-new.$pid again, if the
>   renaming failed.
Incidentally, the dhclient-script performs the move, the stderr output
of the failed mv command does not get properly logged.  I did notice
that systemd will capture it, but I use logcheck (which doesn't look at
the systemd journal) and so did not notice this problem for some time.

> * dhclient prepares resolv.conf.dhclient-new.$pid not in /etc/ but in
>   /tmp/. There it's far less annoying if the directory is cluttered with
>   small files and those files would be usually cleaned up at
>   reboot. (Disavantage: The renaming is often a move from one file
>   system to another -- which might not be wanted.)
I think that this is the best solution.  Could you explain why you think
that the crossing the filesystem boundary is a disadvantage?

> * dnssec-triggerd cleans up those files, either time-based or
>   event-based.
I think this is not the right approach as it results in the files still
being there if dnssec-trigger is not present.



Roberto C. Sánchez

More information about the pkg-dhcp-devel mailing list