Simon Walter <simon@???> writes:
> On 2025-06-13 19:32, Rainer Weikusat via Dng wrote:
>> Simon Walter <simon@???> writes:
>>> Hi all,
>>>
>>> I've noticed in the recent months - maybe as far back as a few years -
>>> that there are changes (to probably debian) that make their way to
>>> devuan and break things.
>>>
>>> A recent example:
>>>
>>> bind log rotation changes cause /var/log to need to be writtable by the
>>> bind user... or so it seems.
>>
>> I'm running bind as local caching resolver on daedalus and it certainly
>> doesn't ship and bind-specific log rotation configuration but just logs
>> via syslog, as it always did.
>
> OK, do you usually update/upgrade your system or install fresh?
>
> I've been upgrading and am now on chimaera. Is there no named.conf.log
> on your system?
>
> root@bind:~# cat /etc/bind/named.conf.log
> logging {
> channel update_debug {
> file "/var/log/update_debug.log" versions 3 size 100k;
> severity debug;
> print-severity yes;
> print-time yes;
> };
> channel security_info {
> file "/var/log/security_info.log" versions 1 size 100k;
> severity info;
> print-severity yes;
> print-time yes;
> };
> channel bind_log {
> file "/var/log/bind.log" versions 3 size 1m;
> severity info;
> print-category yes;
> print-severity yes;
> print-time yes;
> };
>
> category default { bind_log; };
> category lame-servers { null; };
> category update { update_debug; };
> category update-security { update_debug; };
> category security { security_info; };
> };root@bind:~#
>
> The file on my system is from April 2023. Maybe it is leftover from a
> previous system/update.
That's not part of the bind9 package. Considering the content, I think
it probably came from here:
https://wiki.debian.org/Bind9#File_.2Fetc.2Fbind.2Fnamed.conf.log
::
Re: [DNG] how to deal with breaking…
