12-18-2006
Quote:
Originally Posted by silicate
do you have the logrotate setup on a cron job?
I am not sure, but this is what the "ls /etc/cron*" shows:
ls cron*
cron.deny crontab
cron.d:
cron.daily:
beagle-crawl-system suse-clean_catman suse.de-backup-rpmdb suse.de-clean-tmp suse.de-update-preload
logrotate suse.de-backup-rc.config suse.de-check-battery suse.de-cron-local suse-do_mandb
cron.hourly:
mcelog
cron.monthly:
as logrotate is under cron.daily, I assumed it has been set up.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,guys:
recently,i am puzzled by a question .when i create a new file named by /etc/logrotate.d/debug. The cont. is listed as follow:
/var/log/debug {
rotate 3
missingok
notifempty
size=2k
prerotate
/bin/kill -HUP `cat... (0 Replies)
Discussion started by: icehero
0 Replies
2. UNIX for Advanced & Expert Users
HI,
I want a help for Configuring snmpd.conf and snmptrapd.conf (i.e Configuring SNMP)
for receiving
TRAPS in my networks. I am using RHEL4.0 OS.
Please tell me How I can configure above two files in a proper way and at an
advanced level.
Especially I am getting... (2 Replies)
Discussion started by: jagdish.machhi@
2 Replies
3. Solaris
Hello Guys,
Do we need to configure this file only if we add SAN disk or even if we add local disk, do we need to modify? (4 Replies)
Discussion started by: mokkan
4 Replies
4. 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
5. Red Hat
Hi all,
I have to configure the logrotate.conf file on some Linux RedHat servers.
So, by default I seen the file is as follow:
# see "man logrotate" for details
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log files after rotating... (5 Replies)
Discussion started by: idro
5 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. Shell Programming and Scripting
Hello all,
Newbie here.
I'm currently tasked with updating rsyslog.conf and auditd.conf on a large set of servers. I know the exact logging configurations that I want to enable. I have updated both files on on a server and hope to use the updated files as a template for the rest of the... (3 Replies)
Discussion started by: Mide
3 Replies
10. Solaris
Hi,
I've installed Solaris 11.3(live media) and configured DNS. Everytime I reboot the server, resolv.conf got deleted and it created a new nsswitch.conf.
I used below to configure both settings:
# svccfg -s dns/client
svc:/network/dns/client> setprop config/nameserver = (xx.xx.xx.aa... (1 Reply)
Discussion started by: flexihopper18
1 Replies
LEARN ABOUT MOJAVE
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user
can have their own crontab, and they are not intended to be edited directly.
(Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.)
If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the
/usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
/usr/lib/cron/cron.deny file in order to use this command. If neither of these files exists, then depending on site-dependent configuration
parameters, only the super user will be allowed to use this command, or all users will be able to use this command. The format of these
files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for com-
ments.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.
The following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/usr/lib/cron/cron.allow
/usr/lib/cron/cron.deny
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). The new command syntax differs from previous versions of Vixie Cron, as well
as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
December 29, 1993 BSD