04-06-2015
Flitering SYSLOG
is there a way to control producing or generating SYSLOG data?
I'd like SYSLOG to generate only certain data such as update, delete, logon etc.
We have LogRhythm and it doesn't want to store all SYSLOG data generated.
Thanks,
10 More Discussions You Might Find Interesting
1. Solaris
Dear All,
We are going for Disaster Recovery project, the vendor asked for more details about how much is the daily data changes only. using sar / iostat can any one help me to collect this ?!
Note: only I need the changed data size not the daily increasing data. this is to know how much... (1 Reply)
Discussion started by: adel8483
1 Replies
2. Shell Programming and Scripting
I want to connect to one database and collect data from any table using shell script. (0 Replies)
Discussion started by: rinku
0 Replies
3. Shell Programming and Scripting
Hi Friends ,
I am urgently needed your help.
could you pleas help me in creating the shell script.
Requirement :
collect the data from no_file.txt
no_file.txt
============
1
11
265
290
300
313
326
351
Then create another shele script like
my_shell.csh (3 Replies)
Discussion started by: bikas_jena
3 Replies
4. Shell Programming and Scripting
Hi All ,
In my environment we have 12 SAN switches .Culd u pls help me for below queries .
would like to telnet to all switches and collect information in daily basis with "switchstatus" command and store the output under /tmp/ folder on systemA .
To keep passwords of 12switches in a... (1 Reply)
Discussion started by: chinni-script
1 Replies
5. Shell Programming and Scripting
hi all
I am looking for shell script ,by which i need to gather all the DB information in Sybase server .
Thanks in advance :) (3 Replies)
Discussion started by: mvsramarao
3 Replies
6. Shell Programming and Scripting
I have a file current.csv file
2011/05/06 11:12:20 | 16:guest pid=014782 opened Boards 0, 1, 2, 3
2011/05/06 12:23:13 | 16:guest pid=014782 closed
2011/05/06 12:26:05 | 17:guest pid=022383 opened Boards 0, 1, 2, 3
2011/05/06 20:09:04 | 17:guest pid=022383 closed
2011/05/06... (5 Replies)
Discussion started by: sabercats
5 Replies
7. UNIX Desktop Questions & Answers
there are 200 files named file1_0.pdb,file1_60.pdb etc....it looks like:
ATOM 1 N VAL 1 8.897 -21.545 -7.276 1.00 0.00
ATOM 2 H1 VAL 1 9.692 -22.015 -6.868 1.00 0.00
ATOM 3 H2 VAL 1 9.228 -20.766 -7.827 1.00 0.00
ATOM 4 H3 ... (5 Replies)
Discussion started by: kanikasharma
5 Replies
8. Shell Programming and Scripting
I am using AIX 5.3.0.0 ; I need a script to find out each remote AIX boxes
Hostname, Model name and Serial number in following format
Hostname Modelname SerialID
AIXMC01 IBM,7026-B80 IBM,0110BBA1F
AIXMC02 IBM,7026-H50 IBM,0110BBA56
AIXMC03 IBM,7026-H50 IBM,0110BBARR... (12 Replies)
Discussion started by: amir07
12 Replies
9. Shell Programming and Scripting
Hi all,
i have a task to do with Python and because i'm a beginner on it i would like your help on this.
Create a python script that:
Every hour collect the Temperature (e.g. 29C) and Current Condition (e.g. Clear) from this website wunderground.com/global/stations/54511.html
Create a CSV... (0 Replies)
Discussion started by: ragaga123
0 Replies
10. Shell Programming and Scripting
I need to collect last 2 days data from /var/log/messages into a separate file (file format: flmessagetimedaymonth). I have collect today's month, date, time information in separate variable. Please help me in this issue (Probably need awk and grep function).
month=$(date|awk '{print $2}')... (4 Replies)
Discussion started by: makauser
4 Replies
LEARN ABOUT FREEBSD
upssched
UPSSCHED(8) NUT Manual UPSSCHED(8)
NAME
upssched - Timer helper for scheduling events from upsmon
SYNOPSIS
upssched
Note
upssched should be run from upsmon(8) via the NOTIFYCMD. You should never run it directly during normal operations.
DESCRIPTION
upssched was created to allow users to execute programs at times relative to events being monitored by upsmon(8). The original purpose was
to allow for a shutdown to occur after some fixed period on battery, but there are other uses that are possible.
INTEGRATION
upssched needs to be called as the NOTIFYCMD in your upsmon.conf(5). It determines what is happening based on the UPSNAME and NOTIFYTYPE
environment variables. You should never have to deal with them directly.
Set the EXEC flag on the events that you want to see in upssched. For example, to make sure that upssched hears about ONLINE, ONBATT and
LOWBATT events, the flags would look like this:
NOTIFYFLAG ONLINE EXEC
NOTIFYFLAG ONBATT EXEC
NOTIFYFLAG LOWBATT EXEC
If you also want to continue writing to the syslog, just add it in:
NOTIFYFLAG ONLINE SYSLOG+EXEC
NOTIFYFLAG ONBATT SYSLOG+EXEC
NOTIFYFLAG LOWBATT SYSLOG+EXEC
For a full list of notify flags, see the upsmon(8) documentation.
CONFIGURATION
See upssched.conf(5) for information on configuring this program.
EARLY SHUTDOWNS
To shut down the system early, define a timer that starts due to an ONBATT condition. When it triggers, make your CMDSCRIPT call your
shutdown routine. It should finish by calling upsmon -c fsd so that upsmon gets to shut down the slaves in a controlled manner.
Be sure you cancel the timer if power returns (ONLINE).
DEBOUNCING EVENTS
If your UPS goes on and off battery frequently, you can use this program to reduce the number of pager messages that are sent out. Rather
than sending pages directly from upsmon(8), use a short timer here. If the timer triggers with the UPS still on battery, then send the
page. If the power returns before then, the timer can be cancelled and no page is necessary.
BACKGROUND
This program was written primarily to fulfill the requests of users for the early shutdown scenario. The "outboard" design of the program
(relative to upsmon) was intended to reduce the load on the average system. Most people don't have the requirement of shutting down after N
seconds on battery, since the usual OB+LB testing is sufficient.
This program was created separately so those people don't have to spend CPU time and RAM on something that will never be used in their
environments.
The design of the timer handler is also geared towards minimizing impact. It will come and go from the process list as necessary. When a
new timer is started, a process will be forked to actually watch the clock and eventually start the CMDSCRIPT. When a timer triggers, it is
removed from the queue. Cancelling a timer will also remove it from the queue. When no timers are present in the queue, the background
process exits.
This means that you will only see upssched running when one of two things is happening:
o There's a timer of some sort currently running
o upsmon just called it, and you managed to catch the brief instance
The final optimization handles the possibility of trying to cancel a timer when there are none running. If the timer daemon isn't running,
there are no timers to cancel, and furthermore there is no need to start a clock-watcher. So, it skips that step and exits sooner.
FILES
upssched.conf(5)
SEE ALSO
upsmon(8)
Internet resources:
The NUT (Network UPS Tools) home page: http://www.networkupstools.org/
Network UPS Tools 05/21/2012 UPSSCHED(8)