https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=158794

Airell <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #2 from Airell <[email protected]> ---
Running newsyslog with -vvvvv shows a 'default' <default> entry will be made
even if a <default> entry is present in a log file:

/etc/newsyslog.conf.d/default.conf
# logfilename          [owner:group]    mode count size when  flags
<default>                               640  7     100  @T00  JN
somelog.log                             640  7     100  @T00  JN


Processing /etc/newsyslog.conf.d/default.conf
        --> [creating entry for <default>]     <-- This is <default> from conf
        --> [creating entry for somelog.log]   <-- This is somelog.log from
conf
        --> [creating entry for <default>]     <-- This is 'default' <default>
        + No entry matched /var/log/nginx/nginx-access-global.log  (will use
<default>)
...
/var/log/nginx/nginx-access-global.log <3>: size (Kb): 7 [50] --> skipping


Above example shows the size rotation is 50, not 100. So it's probably taking
the last <default> entry, which is the one automatically created:


When removing the <default> line from the config, it shows the 'default'
<default> entry be made:

Processing /etc/newsyslog.conf.d/default.conf
        --> [creating entry for somelog.log]   <-- This is somelog.log from
conf
        --> [creating entry for <default>]     <-- This is 'default' <default>
        + No entry matched /var/log/nginx/nginx-access-global.log  (will use
<default>)
...
/var/log/nginx/nginx-access-global.log <3>: size (Kb): 7 [50] --> skipping


Regards, Airell.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[email protected]"

Reply via email to