Sponsored Content
Full Discussion: Logrotate configuration
Top Forums UNIX for Dummies Questions & Answers Logrotate configuration Post 302897112 by charli1 on Friday 11th of April 2014 02:44:58 AM
Old 04-11-2014
Quote:
Originally Posted by CarloM
I would guess that your filepattern is also matching olddir, so it's rotating everything in there as well.
Thanks for the reply mate,
so you think i will resolve mu issue if i remove the last
Code:
*

on my date pattern match?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

logrotate with /etc/logrotate.conf file

Hi there, I want to rotate the logfiles which are located in /var/log/jboss/tomcat* so I have created a file named as 'tomat' in /etc/logrotate.d/tomcat with the following content. # cat /etc/logrotate.d/tomcat /var/log/jboss/tomcat_access_log*.log { daily nocreate ... (2 Replies)
Discussion started by: skmdu
2 Replies

2. UNIX for Advanced & Expert Users

Logrotate configuration problem

Hi, I have the following configuration file: /logs/system/mindundi/* { rotate 0 daily missingok sharedscripts postrotate find /logs/system/mindundi/ -name "*log" -mtime +15 -exec /bin/rm -f {} \; endscript } I want to save only... (6 Replies)
Discussion started by: mitchbcn
6 Replies

3. Linux

LogRotate

Hi I am trying to rotate specific log by using logrotate function in unix I have made following entry in the /etc/logrotate.conf file /var/log/testlog/debug_log { daily rotate 7 create compress } But only issue is that my other logs like /var/log/messages,... (2 Replies)
Discussion started by: SiddhV
2 Replies

4. UNIX for Advanced & Expert Users

rotate modsec log with logrotate in the global configuration

Hello Experts, I have an apache 2.2.17 on solaris 10 that I am not sure if I, could list the following in the global settings in httpd.conf. I tested it in the Virtual host section of httpd.conf and, it works but, not sure if I can do it in the global settings. Any help would be greatly... (0 Replies)
Discussion started by: afadaghi
0 Replies

5. Red Hat

Logrotate on RHEL 5

Hi All, Can any one let me me know if i run /usr/sbin/logrotate /etc/logrotate.conf will it read the whole /var/log/messages or it just see the time stamp of message file & then rotate the logs. Just wants to know is logrotation based on messages file contents or messages file time stamp. ... (1 Reply)
Discussion started by: ajaincv
1 Replies

6. Shell Programming and Scripting

Logrotate - I am not able to rotate files using logrotate

I have written script which is working in Home directory perfectly and also compressing log files and rotating correctly. But, when i try to run script for /var/log/ i am able to get compressed log files but not able to get rotation of compressed log files. Please suggest. I am using below command... (5 Replies)
Discussion started by: VSom007
5 Replies

7. AIX

Logrotate - /etc/logrotate.conf does't exist

Hi Admins. I have installed logrotate rpm on Aix 6.1. After the installation of rpm, I don't find /etc/logrotate.conf file and /etc/logrotate.d dir . The config file is located in /opt/freeware/etc/logrotate.conf. When I ran logrotate -v /opt/freeware/etc/logrotate.conf I get below... (2 Replies)
Discussion started by: snchaudhari2
2 Replies

8. AIX

Logrotate.conf

Hey Admins, I have installed logrotate on AIX server. I want to configure it for 1. /var/log/messages – keep 90 days, i.e., weekly rotate 13 2. Syslog – keep 90 days i.e., weekly rotate 13 3. Wtmp – keep 90 days i.e., weekly rotate 13 4. Sulog – keep 90 days i.e., weekly rotate 13 What... (1 Reply)
Discussion started by: snchaudhari2
1 Replies

9. Shell Programming and Scripting

Problem with logrotate

Hi, I have a problem with logrotate at Centos 7. My logrotate is configured with "rotate 0" to Apache logs, so it should never keep logs when rotating, just removing them and replacing by new empty ones at every rotation. But for some reason, once in a while, I see that logrotate is creating... (0 Replies)
Discussion started by: dado000
0 Replies

10. UNIX for Dummies Questions & Answers

When to use sharedscripts in a Logrotate Configuration?

Hello All, OS: SLES 11.3 x86_64 Should I be using the sharedscripts config command for my logrotate configuration, given the info below? I made it so the server sending the log data will do Syslog pushes of 3 types of logs to my SLES server, and all 3 logs will be written into the same... (3 Replies)
Discussion started by: mrm5102
3 Replies
NEWSYSLOG.CONF(5)					      BSD File Formats Manual						 NEWSYSLOG.CONF(5)

NAME
newsyslog.conf -- newsyslog(8) configuration file DESCRIPTION
The newsyslog.conf file is used to set log file rotation configuration for the newsyslog(8) utility. Configuration may designate that logs are rotated based on size, last rotation time, or time of day. The newsyslog.conf file can also be used to designate secure permissions to log files at rotation time. During initialization, newsyslog(8) reads a configuration file, normally /etc/newsyslog.conf, to determine which logs may potentially be rotated and archived. Each line has five mandatory fields and four optional fields, separated with whitespace. Blank lines or lines beginning with '#' are ignored. If '#' is placed in the middle of the line, the '#' character and the rest of the line after it is ignored. To prevent special meaning, the '#' character may be escaped with ''; in this case preceding '' is removed and '#' is treated as an ordinary character. The fields of the configuration file are as follows: logfile_name Name of the system log file to be archived, or the literal string ``<default>''. The special default entry will only be used if a log file name is given as a command line argument to newsyslog(8), and if that log file name is not matched by any other line in the configuration file. owner:group This optional field specifies the owner and group for the archive file. The ':' is essential regardless if the owner or group field is left blank or contains a value. The field may be numeric, or a name which is present in /etc/passwd or /etc/group. By default, log files are owned by root:admin. mode Specify the file mode of the log file and archives. count Specify the maximum number of archive files which may exist. This does not consider the current log file. size When the size of the log file reaches size in kilobytes, the log file will be trimmed as described above. If this field contains an asterisk ('*'), the log file will not be trimmed based on size. when The when field may consist of an interval, a specific time, or both. If the when field contains an asterisk ('*'), log rotation will solely depend on the contents of the size field. Otherwise, the when field consists of an optional interval in hours, usually fol- lowed by an '@'-sign and a time in restricted ISO 8601 format. Additionally, the format may also be constructed with a '$' sign along with a rotation time specification of once a day, once a week, or once a month. If a time is specified, the log file will only be trimmed if newsyslog(8) is run within one hour of the specified time. If an inter- val is specified, the log file will be trimmed if that many hours have passed since the last rotation. When both a time and an interval are specified then both conditions must be satisfied for the rotation to take place. There is no provision for the specification of a timezone. There is little point in specifying an explicit minutes or seconds compo- nent in the current implementation, since the only comparison is ``within the hour''. ISO 8601 restricted time format: The lead-in character for a restricted ISO 8601 time is an '@' sign. The particular format of the time in restricted ISO 8601 is: [[[[[cc]yy]mm]dd][T[hh[mm[ss]]]]]. Optional date fields default to the appropriate component of the current date; optional time fields default to midnight; hence if today is January 22, 1999, the following date specifications are all equivalent: '19990122T000000' '990122T000000' '0122T000000' '22T000000' 'T000000' 'T0000' 'T00' '22T' 'T' '' Day, week, and month time format: The lead-in character for day, week, and month specification is a '$' sign. The particular format of day, week, and month specifica- tion is: [Dhh], [Ww[Dhh]], and [Mdd[Dhh]], respectively. Optional time fields default to midnight. The ranges for day and hour specifications are: hh hours, range 0..23 w day of week, range 0..6, 0 = Sunday dd day of month, range 1..31, or one of the letters 'L' or 'l' to specify the last day of the month. Some examples: $D0 rotate every night at midnight (same as @T00) $D23 rotate every day at 23:00 (same as @T23) $W0D23 rotate every week on Sunday at 23:00 $W5D16 rotate every week on Friday at 16:00 $M1D0 rotate at the first day of every month at midnight (i.e., the start of the day; same as @01T00) $M5D6 rotate on every 5th day of month at 6:00 (same as @05T06) flags This optional field is made up of one or more characters that specify any special processing to be done for the log files matched by this line. The following are valid flags: B indicates that the log file is a binary file, or has some special format. Usually newsyslog(8) inserts an ASCII message into a log file during rotation. This message is used to indicate when, and sometimes why the log file was rotated. If B is specified, then that informational message will not be inserted into the log file. C indicates that the log file should be created if it does not already exist, and if the -C option was also specified on the command line. D indicates that newsyslog(8) should set the UF_NODUMP flag when creating a new version of this log file. This option would affect how the dump(8) command treats the log file when making a file system backup. G indicates that the specified logfile_name is a shell pattern, and that newsyslog(8) should archive all filenames matching that pattern using the other options on this line. See glob(3) for details on syntax and matching rules. J indicates that newsyslog(8) should attempt to save disk space by compressing the rotated log file using bzip2(1). N indicates that there is no process which needs to be signaled when this log file is rotated. U indicates that the file specified by path_to_pid_file will contain the ID for a process group instead of a process. This option also requires that the first line in that file be a negative value to distinguish it from a process ID. Z indicates that newsyslog(8) should attempt to save disk space by compressing the rotated log file using gzip(1). - a minus sign will not cause any special processing, but it can be used as a placeholder to create a flags field when you need to specify any of the following fields. path_to_pid_file This optional field specifies the file name containing a daemon's process ID or to find a group process ID if the U flag was speci- fied. If this field is present, a signal_number is sent the process ID contained in this file. If this field is not present, then a SIGHUP signal will be sent to syslogd(8), unless the N flag has been specified. This field must start with '/' in order to be recog- nized properly. signal_number This optional field specifies the signal number that will be sent to the daemon process (or to all processes in a process group, if the U flag was specified). If this field is not present, then a SIGHUP signal will be sent. SEE ALSO
bzip2(1), gzip(1), syslog(3), chown(8), newsyslog(8), syslogd(8) HISTORY
This manual page first appeared in FreeBSD 4.10. BSD
November 27, 2006 BSD
All times are GMT -4. The time now is 02:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy