Hide Forgot
As reported in bug 723547, the parsing of the "size" configuration option is currently broken in logrotate. If that is fixed, a configuration file that has both a "size" configuration and a time configuration like "weekly", only the latest will take effect. The first one would be silently ignored. The documentation properly states that the two configurations are mutually exclusive. But it seems it would make sense to issue a diagnostic if this is done. I suggest to add this as an enhancement to logrotate.
I'm closing this as duplicate of 723797 (although it's newer bug) *** This bug has been marked as a duplicate of bug 723797 ***
Does that mean you plan to make the "size" directive and a time limit able to coexist, with the semantics that rotation is done when either is triggered? If so, it makes sense to merge them, even though they aren't strictly speaking duplicates. One COULD fix this one by adding a diagnostic, and fix bug 723797 by introducing a new directive, separate from both size and minsize. Letting the old directives keep their current semantics.
(In reply to comment #2) > Does that mean you plan to make the "size" directive and a time limit able to > coexist, with the semantics that rotation is done when either is triggered? If > so, it makes sense to merge them, even though they aren't strictly speaking > duplicates. > > One COULD fix this one by adding a diagnostic, and fix bug 723797 by > introducing a new directive, separate from both size and minsize. Letting the > old directives keep their current semantics. Yes, that's what I'm going to do (or at least give it a try), but I will have to find time to do it. What exactly do you mean by diagnostic?
(In reply to comment #3) > Yes, that's what I'm going to do Ok, then the duplicate relation makes sense. > but I will have to find time I know what you mean! :-/ > What exactly do you mean by diagnostic? Nothing specific, just SOME kind of error message. As it is today, logrotate silently ignores that the first directive. I would prefer if it printed an warning message it does it. But of course, if it stops ignoring it instead, there is no reason to print any message.