Scripts for monitoring real time for the error code Post: 41446

Sponsored Content

Operating Systems HP-UX Scripts for monitoring real time for the error code Post 41446 by Perderabo on Monday 6th of October 2003 12:55:33 PM

10-06-2003

Administrator Emeritus

You still have specified what errors you are looking to monitor. I'll guess that you want to monitor /var/adm/messages for anything.

From your thread in the Linux forum, I gather that you are writing in C++. You can use fstat() or stat() to see if the file has been changed. But you must repeatedly invoke fstat(). Let's say that you want your program to notice a new error message in less than a millisecond. Then 1000 times each second you must fstat() that file. That is quite a load for the box. Even HP's fastest cpu will spend a high percentage of it's time doing that. Most realtime applications can tolerate a millisecond delay so I'm guessing that this would be enough. Now suppose that you can tolerate a one second delay between the arrivial of the error message and your program noticing it. That would reduce the load on the box by a factor of 1000. At this point the cpu can do some other things. Most of us will actually tolerate 2 or 3 minutes in a situation like this. Some of us would even go as high as 5 minutes. But it's your box, you can loop as fast as you want.

Perderabo

View Public Profile for Perderabo

Find all posts by Perderabo

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

EPOCH to real time?

hi all :confused: i am wondering if there is a way to convert from EPOCH time to the standard tim, may be using a script or some thing else??????? thanks............................

2. UNIX for Dummies Questions & Answers

capturing real time

Newbie question: I wrote korn shell script that lets me connect to a cisco switch thru telnet from sun server. I'm wodering if or what command i would use to capture info that is being sent to standard output when the script is running. Putting part of my script below and results. #!/bin/ksh...

3. Shell Programming and Scripting

DR monitoring shell scripts

Hi All, we need to have 2 scripts in place for the following:. 1) One which will verify if archive log sequence in Production is getting replicated in DR or not. If there is difference, we should receive an email. 2)If there are any errors in DR site like in alert log, mail should be sent to...

4. Shell Programming and Scripting

Shell script to convert epoch time to real time

Dear experts, I have an epoch time input file such as : - 1302451209564 1302483698948 1302485231072 1302490805383 1302519244700 1302492787481 1302505299145 1302506557022 1302532112140 1302501033105 1302511536485 1302512669550 I need the epoch time above to be converted into real...

5. Shell Programming and Scripting

Converting real time to epoch time

# date +%s -d "Mon Feb 11 02:26:04" 1360567564 # perl -e 'print scalar localtime(1360567564), "\n";' Mon Feb 11 02:26:04 2013 the epoch conversion is working fine. but one of my application needs 13 digit epoch time as input 1359453135154 rather than 10 digit epoch time 1360567564...

LEARN ABOUT MOJAVE

tping

TPING(1)                                                           LAM COMMANDS                                                           TPING(1)

NAME

       tping - Send echo messages to LAM nodes.

SYNOPSIS

       tping [-hv] [-c count] [-d delay] [-l length] nodes

OPTIONS

       -h            Print the command help menu.

       -v            Turn OFF verbose mode.

       -c count      Send count messages.

       -d delay      Delay delay seconds between each message.

       -l length     Each message is length bytes long.

DESCRIPTION

       The  tping  command  sends  messages  to,  and  collects replies from, a list of nodes, via the LAM echo server.  It is similar to the UNIX
       ping(8) command, and is used as a quick diagnosis of the LAM network.

       Unless options are specified, tping sends a 1 byte message an infinite number of times, displaying the roundtrip time of each message as it
       completes,  with  a delay of 1 second between roundtrips.  After the loop is broken (with keyboard interrupt, eg: ^C), tping prints statis-
       tics about all roundtrip messages.

EXAMPLES

       tping h
           Echo messages to the local node.

       tping -v n7 -l 1000 -c 10
           Echo 1000 byte messages to node 7.  Stay silent while working.  Stop after 10 roundtrips and report statistics.

BUGS

       There is no built-in timeout and tping will wait forever to receive an echo.  If no echo is received, due to a dead  link  or  node,  tping
       hangs.   Stop  the  process  with  a  keyboard suspend signal (eg: ^Z) and terminate LAM with lamhalt(1) or lamwipe(1) (although the use of
       lamwipe(1) is deprecated).

SEE ALSO

       lamhalt(1), lamwipe(1)

LAM 7.1.4                                                           July, 2007                                                            TPING(1)