I read documentation e I've just done my script to handle my monitoring log files, that it's simply as follow:
This times I hope not to make a wrong question, but I didn't really understand how to synchronize my monitoring.sh custom script (see post below) and the actions of logrotate on monitoring.log.
Maybe logrotate starts at the end of monitoring.sh, or not?
THX
Last edited by pludi; 03-25-2010 at 08:53 AM..
Reason: code tags, please!
I changed the logrotate.conf file to make a new log file to be automatically rotated daily. But after a night, I have not seen the rotated file.
When does this rotation happen? I mean what is the exact time?
In addition, do I have to restart what deamon to make the change take effect? (10 Replies)
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)
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)
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)
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)
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)
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)
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 DEBIAN
sensors-detect
SENSORS-DETECT(8) System Manager's Manual SENSORS-DETECT(8)NAME
sensors-detect - detect hardware monitoring chips
SYNOPSIS
sensors-detect
DESCRIPTION
sensors-detect is an interactive program that will walk you through the process of scanning your system for various hardware monitoring
chips, or sensors, supported by libsensors(3), or more generally by the lm_sensors tool suite.
sensors-detect will look for the following devices, in order:
o Sensors embedded in CPUs, south bridges and memory controllers.
o Sensors embedded in Super I/O chips.
o Hardware monitoring chips accessed through ISA I/O ports.
o Hardware monitoring chips reachable over the SMBus or more generally any I2C bus on your system.
As the last two detection steps can cause trouble on some systems, they are normally not attempted if the second detection step led to the
discovery of a Super I/O chip with complete hardware monitoring features. However, the user is always free to ask for all detection steps
if so is his/her wish. This can be useful if a given system has more than one hardware monitoring chip. Some vendors are known to do this,
most notably Asus and Tyan.
WARNING
sensors-detect needs to access the hardware for most of the chip detections. By definition, it doesn't know which chips are there before
it manages to identify them. This means that it can access chips in a way these chips do not like, causing problems ranging from SMBus
lockup to permanent hardware damage (a rare case, thankfully.)
The authors made their best to make the detection as safe as possible, and it turns out to work just fine in most cases, however it is
impossible to guarantee that sensors-detect will not lock or kill a specific system. So, as a rule of thumb, you should not run sensors-
detect on production servers, and you should not run sensors-detect if can't afford replacing a random part of your system. Also, it is
recommended to not force a detection step which would have been skipped by default, unless you know what you are doing.
SEE ALSO sensors(1), libsensors(3)AUTHOR
Frodo Looijaard and Jean Delvare
lm-sensors 3 December 2008 SENSORS-DETECT(8)