Control: tags -1 fixed-upstream
Hello,
Thank you for your report.
> totally reproducable is the issue that with something like
>
> dateformat<tab>-%Y-%m-%d
>
> (with "<tab>" meaning tab character "0x09") a logfile
>
> logfile.log
>
> is rotated into a file
>
> logfile.log<tab>-2021-04-19
>
> in contrast to the statement in the logrotate.conf man page that keys
> and value are separated by whitespace and/or an optional equal ("=")
> sign.
This has been fixed upstream in
https://github.com/logrotate/logrotate/commit/eb70637107aa6946b256e35fbfe68a387318c278
> If I remember correctly I also get an error message if I use the config
> keyword "rotate" like "rotate<tab>7" with daily rotation. A
> "copytruncate" possibly also plays a role.
I could not reproduce any error using a tab as separator here.
