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
Old 10-06-2003
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.
 

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............................ (5 Replies)
Discussion started by: TheEngineer
5 Replies

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... (2 Replies)
Discussion started by: wisher115
2 Replies

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... (1 Reply)
Discussion started by: a1_win
1 Replies

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... (4 Replies)
Discussion started by: aismann
4 Replies

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... (3 Replies)
Discussion started by: vivek d r
3 Replies
SA(8)							      System Manager's Manual							     SA(8)

NAME
sa, accton - system accounting SYNOPSIS
sa [ -abcdDfijkKlnrstu ] [ -v threshold ] [ -S savacctfile ] [ -U usracctfile ] [ file ] accton [ file ] DESCRIPTION
With an argument naming an existing file, accton causes system accounting information for every process executed to be placed at the end of the file. If no argument is given, accounting is turned off. Sa reports on, cleans up, and generally maintains accounting files. Sa is able to condense the information in /usr/adm/acct into a summary file /usr/adm/savacct which contains a count of the number of times each command was called and the time resources consumed. This condensation is desirable because on a large system /usr/adm/acct can grow by 100 blocks per day. The summary file is normally read before the accounting file, so the reports include all available information. If a file name is given as the last argument, that file will be treated as the accounting file; /usr/adm/acct is the default. Output fields are labeled: "cpu" for the sum of user+system time (in minutes), "re" for real time (also in minutes), "k" for cpu-time aver- aged core usage (in 1k units), "avio" for average number of i/o operations per execution. With options fields labeled "tio" for total i/o operations, "k*sec" for cpu storage integral (kilo-core seconds), "u" and "s" for user and system cpu time alone (both in minutes) will sometimes appear. There are near a googol of options: a Print all command names, even those containing unprintable characters and those used only once. By default, those are placed under the name `***other.' b Sort output by sum of user and system time divided by number of calls. Default sort is by sum of user and system times. c Besides total user, system, and real time for each command print percentage of total time over all commands. d Sort by average number of disk i/o operations. D Print and sort by total number of disk i/o operations. f Force no interactive threshold compression with -v flag. i Don't read in summary file. j Instead of total minutes time for each category, give seconds per call. k Sort by cpu-time average memory usage. K Print and sort by cpu-storage integral. l Separate system and user time; normally they are combined. m Print number of processes and number of CPU minutes for each user. n Sort by number of calls. r Reverse order of sort. s Merge accounting file into summary file /usr/adm/savacct when done. t For each command report ratio of real time to the sum of user and system times. u Superseding all other flags, print for each command in the accounting file the user ID and command name. v Followed by a number n, types the name of each command used n times or fewer. Await a reply from the terminal; if it begins with `y', add the command to the category `**junk**.' This is used to strip out garbage. S The following filename is used as the command summary file instead of /usr/adm/savacct. U The following filename is used instead of /usr/adm/usracct to accumulate the per-user statistics printed by the -m option. FILES
/usr/adm/acct raw accounting /usr/adm/savacct summary /usr/adm/usracct per-user summary SEE ALSO
ac(8), acct(2) BUGS
The number of options to this program is absurd. 4th Berkeley Distribution November 16, 1996 SA(8)
All times are GMT -4. The time now is 12:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy