On Mon, Nov 18, 2013 at 8:42 AM, Paul Martin <p...@debian.org> wrote:
>
>
> On Sun, Nov 17, 2013 at 06:31:06PM -0700, Ben Hildred wrote:
> > Severity: normal
> >
> > this affects users upgrading their systems from versions which did not
> have
> > this option.
>
> No, it doesn't! You'd have to manually add the option to any existing
> scripts, which would otherwise continue to run exactly as before
> without any need for modification.
>
> but at increased volume
This is a "minor" bug because it solely concerns documentation of a
> newly added feature which doesn't break any existing installations.
>
> every server emailed every day about every create option
> > The point of this bug report is not to say the option is bad, or
> > mis-implemented, it is that there was a significant change in behavior
> with
> > little documentation and no examples of the critical interactions, or
> > recommended practice. I after more than half day got my machine to quit
> > complaining, but I am not confident that my solution is the right one. I
> > think I figured It out, but real documentation would be better.
>
> Please explain what you don't comprehend about the manpage entry
>
> su user group
> Rotate log files set under this user and group instead of
> using
> default user/group (usually root). user specifies the user
> name
> used for rotation and group specifies the group used for
> rota‐
> tion.
>
> and can you suggest a better alternative?
>
> by its self it is fine, but what about create which also makes perfect
sense by it's self but what one arth do they have to do with each other?
create mode owner group
Immediately after rotation (before the postrotate
script is run) the log file is created (with the same name as the log
file just
rotated). mode specifies the mode for the log file in octal
(the same as chmod(2)), owner specifies the user name who will own the log
file, and group specifies the group the log file will belong
to. Any of the log file attributes may be omitted, in which case those
attributes
for the new file will use the same values as the original log
file for the omitted attributes. This option can be disabled using the
nocreate
option.
on first reading it looks like they have little in common, and I don't see
where it says "when using create you must use su with the same options to
suppress error messages" which appears to be the case, and mostly redundant
and confusing where it is not redundant.
--
> Paul Martin <p...@debian.org>
>
--
--
Ben Hildred
Automation Support Services
303 815 6721
