newsyslog configuration/s

[bgroper]

It seems any configurations included in /usr/local/etc/newsyslog.d/*.conf do NOT override the defaults contained in /etc/newsyslog.conf.
Rather, configurations included in /usr/local/etc/newsyslog.d/*.conf appear to be processed in addition to whatever is contained in /etc/newsyslog.conf.
Could this be deliberate ? Perhaps some unusual FreeBSD behaviour.
Edit. Using 14.3, not tested any other version/s.

 

[tembun]

The behaviour you described is correct and documented in newsyslog(8):

/usr/local/etc/newsyslog.conf.d  By default each file in this directory ending in '.conf' and not beginning
                                 with '.' will be included by the default newsyslog.conf.

 

[Emrion]

Nothing is said in the manual pages concerning the override of an existing value.

Dan got the same result than you even in /etc/newsyslog.d/: https://dan.langille.org/2025/10/01...onf-with-etc-newsyslog-conf-d-newsyslog-conf/

I don't know if it is expected or not. I see nothing on bugzilla, but you should make a PR. You will get an answer.

 

[freebsd_lg]

This behavior is planned.
less /usr/src/usr.sbin/newsyslog/newsyslog.c
...
static void
expand_globs(struct cflist *work_p, struct cflist *glob_p)
{
...

/*
* The worklist contains all fully-specified (non-GLOB) names.
*
* Now expand the list of filename-pattern (GLOB) entries into
* a second list, which (by definition) will only match files
* that already exist. Do not add a glob-related entry for any
* file which already exists in the fully-specified list.

...

 

[bgroper]

Thanks for replies.
I'll try to remember that for some package/s, custom configurations saved in /usr/local/etc/ do NOT always override the default settings that come shipped in /etc/