On Mon, Nov 18, 2013 at 12:22:00PM -0700, Ben Hildred wrote:
> > 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.
I'll amend it with the next upload. The text will read:
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. If the user/group you specify here does not have suffi‐
cient privilege to make files with the ownership you've speci‐
fied in a create instruction, it will cause an error.
--
Paul Martin <p...@debian.org>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
