I am currently using SNMP on Nagios to monitor Exim and all is running great with the exception to it picking up the date / time of the last Exim queue run.
What I am hoping to achieve is for SNMP / Nagios to correctly pickup the difference between the current time and the last queue run.
I am using the below to capture the date / time value ;
However, when I check the snmp, it only takes the first value from the time (: works as a break);
As you can see from my code above I am only trying to get it to display the last date / time as I have no idea where to start with subtracting the values.
I have to do a lot of reporting for the company that I work for and was wondering if anyone had suggestions for a way to create professional looking reports. I currently use Filepro so much that I rarely see the shell. Any help is appreciated. (3 Replies)
Hi everyone, I'm completely new to the board and to UNIX and I have the following question regarding a script I am building.
I am trying to copy an entire directory into a new directory and I was wondering if there is any way of printing on screen a progress report, for example a percentage. It... (9 Replies)
Hi:-
I am working on an audit report that produces a monthly summary of account activity on a particular AIX host. I am struggling with su activity and failed logins as these tend to come back with more then a month's data.
Is there a easy way that these files can be rotated/cleaned out on a... (1 Reply)
Hi ,
Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (0 Replies)
Hi ,
Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (1 Reply)
Hi,
I am using SCO UNIX version 6.0.0 release 5. I am using du and df space to see the used space in the / partition. I am using du -k option to get count in 1024 k so that it directly makes kb. In dfspace I subtracted the used mb from total size mb which should be the used space and then... (40 Replies)
I am having a problem with an SNMP event, and I am not sure where I should be looking to solve this problem.
Description:
There is an SNMP event in our system that for one reason or another is not getting sent out as an email because it is never getting to our SNMP agent.
I see where the... (0 Replies)
Dear Champs,
I am new to unix, and need to configure linux server to send below traps to a SNMP server.
Monitoring TRAP Disk Space Low
Monitoring TRAP Memory Low
Monitoring TRAP CPU high
Monitoring TRAP Admin login/Logoff
Please help me how to send this information to my SNMP server... (2 Replies)
i am working with embedded system -Dell DCS management sub system. my question is as below:
currently we are using linux kernel 2.6.30 build and we have a kernel logs stored to the /var/log/messages path. now we have to transfer all this logs to the specified SNMP target as a part of SNMP... (4 Replies)
Discussion started by: vipul_prajapati
4 Replies
LEARN ABOUT CENTOS
exiwhat
EXIWHAT(8) System Manager's Manual EXIWHAT(8)NAME
exiwhat - Finding out what Exim processes are doing
SYNOPSIS
exiwhat
DESCRIPTION
On operating systems that can restart a system call after receiving a signal (most modern OS), an Exim process responds to the SIGUSR1 sig-
nal by writing a line describing what it is doing to the file exim-process.info in the Exim spool directory. The exiwhat script sends the
signal to all Exim processes it can find, having first emptied the file. It then waits for one second to allow the Exim processes to react
before displaying the results. In order to run exiwhat successfully you have to have sufficient privilege to send the signal to the Exim
processes, so it is normally run as root.
Unfortunately, the ps command which exiwhat uses to find Exim processes varies in different operating systems. Not only are different
options used, but the format of the output is different. For this reason, there are some system configuration options that configure
exactly how exiwhat works. If it doesn't seem to be working for you, check the following compile-time options:
EXIWHAT_PS_CMD
the command for running "ps"
EXIWHAT_PS_ARG
the argument for "ps"
EXIWHAT_EGREP_ARG
the argument for "egrep" to select from "ps" output
EXIWHAT_KILL_ARG
the argument for the "kill" command
An example of typical output from exiwhat is
164 daemon: -q1h, listening on port 25
10483 running queue: waiting for 0tAycK-0002ij-00 (10492)
10492 delivering 0tAycK-0002ij-00 to mail.ref.example [10.19.42.42]
(editor@ref.example)
10592 handling incoming call from [192.168.243.242]
10628 accepting a local non-SMTP message
The first number in the output line is the process number. The third line has been split here, in order to fit it on the page.
BUGS
This manual page needs a major re-work. If somebody knows better groff than us and has more experience in writing manual pages, any patches
would be greatly appreciated.
SEE ALSO exim(8), /usr/share/doc/exim4-base/
AUTHOR
This manual page was stitched together from spec.txt by Andreas Metzler <ametzler at downhill.at.eu.org>, for the Debian GNU/Linux system
(but may be used by others).
March 26, 2003 EXIWHAT(8)