logrotate v2.3

logrotate v2.3

Post by Michael Faur » Tue, 08 Jul 1997 04:00:00



I'm having some difficulty with logrotate v2.3 as included with
RedHat v4.2.

In particular, I can't seem to get the "create" command to honor my
request to create a new log with the permissions I want.

For example:

-----------------------------------------------------------------------------

/usr/lib/news/local/gup/gup.log {
    create 666 gup news
    compress
    daily
    rotate 5

Quote:}

-----------------------------------------------------------------------------

When logrotate actually rotates this log file, it recreates the file
with permissions of 644 instead of 666 as requested.

User ownership and group ownership are done correctly however--it
just doesn't use the right permissions.

What's even more baffling is when I run logrotate with the debug
option (-d) it seems to indicate that it is parsing my configuration
file okay:

-----------------------------------------------------------------------------

reading config file /etc/logrotate.conf
including /etc/logrotate.d
[...]
reading config file gup
reading config info for /usr/lib/news/local/gup/gup.log
[...]
rotating: /usr/lib/news/local/gup/gup.log after 1 days (5 rotations)
empty log files are rotated errors will be mailed to root old logs are
removed log needs rotating renaming /usr/lib/news/local/gup/gup.log.5.gz
to /usr/lib/news/local/gup/gup.log.6.gz renaming
/usr/lib/news/local/gup/gup.log.4.gz to
/usr/lib/news/local/gup/gup.log.5.gz renaming
/usr/lib/news/local/gup/gup.log.3.gz to
/usr/lib/news/local/gup/gup.log.4.gz renaming
/usr/lib/news/local/gup/gup.log.2.gz to
/usr/lib/news/local/gup/gup.log.3.gz renaming
/usr/lib/news/local/gup/gup.log.1.gz to
/usr/lib/news/local/gup/gup.log.2.gz
removing old log /usr/lib/news/local/gup/gup.log.6.gz
renaming /usr/lib/news/local/gup/gup.log to /usr/lib/news/local/gup/gup.log.1
creating new log mode = 0666 uid = 80 gid = 13
compressing new log with: gzip -9 /usr/lib/news/local/gup/gup.log.1

-----------------------------------------------------------------------------

--
+------------------+-------------------------------+-------------------------+

+------------------+-------------------------------+-------------------------+
| In the future, we will put pointy things next to bumpy things. --D.Byrne   |
+----------------------------------------------------------------------------+

 
 
 

1. logrotate v2.3

I'm having some difficulty with logrotate v2.3 as included with
RedHat v4.2.

In particular, I can't seem to get the "create" command to honor my
request to create a new log with the permissions I want.

For example:

-----------------------------------------------------------------------------

/usr/lib/news/local/gup/gup.log {
    create 666 gup news
    compress
    daily
    rotate 5

-----------------------------------------------------------------------------

When logrotate actually rotates this log file, it recreates the file
with permissions of 644 instead of 666 as requested.

User ownership and group ownership are done correctly however--it
just doesn't use the right permissions.

What's even more baffling is when I run logrotate with the debug
option (-d) it seems to indicate that it is parsing my configuration
file okay:

-----------------------------------------------------------------------------

reading config file /etc/logrotate.conf
including /etc/logrotate.d
[...]
reading config file gup
reading config info for /usr/lib/news/local/gup/gup.log
[...]
rotating: /usr/lib/news/local/gup/gup.log after 1 days (5 rotations)
empty log files are rotated errors will be mailed to root old logs are
removed log needs rotating renaming /usr/lib/news/local/gup/gup.log.5.gz
to /usr/lib/news/local/gup/gup.log.6.gz renaming
/usr/lib/news/local/gup/gup.log.4.gz to
/usr/lib/news/local/gup/gup.log.5.gz renaming
/usr/lib/news/local/gup/gup.log.3.gz to
/usr/lib/news/local/gup/gup.log.4.gz renaming
/usr/lib/news/local/gup/gup.log.2.gz to
/usr/lib/news/local/gup/gup.log.3.gz renaming
/usr/lib/news/local/gup/gup.log.1.gz to
/usr/lib/news/local/gup/gup.log.2.gz
removing old log /usr/lib/news/local/gup/gup.log.6.gz
renaming /usr/lib/news/local/gup/gup.log to /usr/lib/news/local/gup/gup.log.1
creating new log mode = 0666 uid = 80 gid = 13
compressing new log with: gzip -9 /usr/lib/news/local/gup/gup.log.1

-----------------------------------------------------------------------------

--
+------------------+-------------------------------+-------------------------+

+------------------+-------------------------------+-------------------------+
| In the future, we will put pointy things next to bumpy things. --D.Byrne   |
+----------------------------------------------------------------------------+

2. Sun login system file

3. v2.4.1-v2.4.3pre2 doesnt power off by halt or shutdown -h

4. searching /etc/rc.d/rc.local file in SuSE6.0

5. SCO Foxbase+ v2.1.1 To v2.1.2

6. Hang on installation; FreeBSD 2.2.5

7. IO Overflow via putc() in GCC v2.6.3, Slackware v2.x Linux v1.2.11

8. Optimizing use of malloc

9. Problems with v2.1.30-v2.1.34

10. Q: gcc v2.8.0 on solaris v2.5.1

11. Slackware Update - v2.0 to v2.1

12. solaris x86 v2.5 vs. v2.5.1 performance

13. Glibc V2.1.2 or V2.1.3?