04-04-2008
I'm not exactly sure, but in the man pages it says :
Quote:
Note that comments may appear anywhere in the config file as long as the first non-whitespace character on the line is a #.
, so I assume you can just comment those out, restart logrotate and see if it works. Don't forget to copy the original conf file.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am getting this system message:
/etc/cron.daily/logrotate:
error: rsync:7 unknown option 'endscript' -- ignoring line
I don't find anything related to rsync in the logrotate.conf file, so I am unsure as to how to resolve this and stop this message.
Thanks. (1 Reply)
Discussion started by: manouche
1 Replies
2. Red Hat
Hi all,
I have configured logrotate to logorotate every 12 hour. The configurations are as follows.
/etc/cron.d/config
-------------------------
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=""
HOME=/root
0 */12 * * * root logrotate /etc/logrotate.d/test
... (1 Reply)
Discussion started by: rsravi74
1 Replies
3. UNIX for Advanced & Expert Users
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
4. Linux
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
5. SuSE
Hi all
We've had new servers coming in and one of the requirement was to keep logs for up to 8 months. I know logrotate can do the job, but by default (on Suse Enterprise10, 11) we have these logs in /etc/logrotate.d dir as default logs which are rotated:
-rw-r--r-- 1 root root 140 Jul... (0 Replies)
Discussion started by: hedkandi
0 Replies
6. Shell Programming and Scripting
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
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
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. UNIX for Dummies Questions & Answers
Hi all,
i would like to have a configuration on log rotate that will gzip my log files with date pattern %Y-%m-%d
move these files to an olddir, but i want to avoid that the logrotate removes my files from old dir newer than 180 days
i applyied this config
#logrotate config to compress files... (3 Replies)
Discussion started by: charli1
3 Replies
10. Shell Programming and Scripting
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
LEARN ABOUT MOJAVE
git-stripspace
GIT-STRIPSPACE(1) Git Manual GIT-STRIPSPACE(1)
NAME
git-stripspace - Remove unnecessary whitespace
SYNOPSIS
git stripspace [-s | --strip-comments]
git stripspace [-c | --comment-lines]
DESCRIPTION
Read text, such as commit messages, notes, tags and branch descriptions, from the standard input and clean it in the manner used by Git.
With no arguments, this will:
o remove trailing whitespace from all lines
o collapse multiple consecutive empty lines into one empty line
o remove empty lines from the beginning and end of the input
o add a missing
to the last line if necessary.
In the case where the input consists entirely of whitespace characters, no output will be produced.
NOTE: This is intended for cleaning metadata, prefer the --whitespace=fix mode of git-apply(1) for correcting whitespace of patches or
files in the repository.
OPTIONS
-s, --strip-comments
Skip and remove all lines starting with comment character (default #).
-c, --comment-lines
Prepend comment character and blank to each line. Lines will automatically be terminated with a newline. On empty lines, only the
comment character will be prepended.
EXAMPLES
Given the following noisy input with $ indicating the end of a line:
|A brief introduction $
| $
|$
|A new paragraph$
|# with a commented-out line $
|explaining lots of stuff.$
|$
|# An old paragraph, also commented-out. $
| $
|The end.$
| $
Use git stripspace with no arguments to obtain:
|A brief introduction$
|$
|A new paragraph$
|# with a commented-out line$
|explaining lots of stuff.$
|$
|# An old paragraph, also commented-out.$
|$
|The end.$
Use git stripspace --strip-comments to obtain:
|A brief introduction$
|$
|A new paragraph$
|explaining lots of stuff.$
|$
|The end.$
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-STRIPSPACE(1)