10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
I'm curious to know how do I add an empty log file (test1.log) to an existing text file to monitor all the changes made to a.txt.
Is this expression
export PATH=$PATH:/home/test1.log
right to be added to the text file a.txt? (5 Replies)
Discussion started by: TestKing
5 Replies
2. Shell Programming and Scripting
Hi,
I want to monitor a log file using tail -f command and search for a specific string on the most recent entry from the file. If the search string matches with the most recent or last line from the file, I want send an email to the people with the message.
tail -f service.log|tail -n 1
... (5 Replies)
Discussion started by: svajhala
5 Replies
3. Shell Programming and Scripting
Hi,
Have written a script to monitor linux non standard log file based on line numbers, so each check store $otalinenum ..
then in next check after 10 minutes it compre the current_total_line_num > last_total_line_num then it will parse the log file from last_total_line_num to... (0 Replies)
Discussion started by: Shirishlnx
0 Replies
4. Shell Programming and Scripting
This is my log file and this is live log.
Any abnormal error other than following
I need to generate the email.
Log path : /DER/app/admin/ABC/bdump/erg.log
Current log# 2 seq# 103046 mem# 0: /ora2/oradata/ABC/redo02a.log
Current log# 2 seq# 103046 mem# 1:... (1 Reply)
Discussion started by: hishanms
1 Replies
5. HP-UX
AM in need of some plugin/script that can monitor HP-UX file "/var/opt/resmon/log/event.log" .
Have written a scrip in sh shell that is working fine for syslog.log and mail.log as having standard format, have interrogated that to Nagios and is working as I required .
But same script failed to... (3 Replies)
Discussion started by: Shirishlnx
3 Replies
6. Shell Programming and Scripting
Hi Friends,
I am trying to write a script which continiously monitor one specific error message from a log file. This script should continiously monitor the file for the error and send out the email when detect the error message. I tried the below command but fails. Please help me.
tail -f... (4 Replies)
Discussion started by: arumon
4 Replies
7. Shell Programming and Scripting
Hi Folks,
I need help in creating a script to monitor a continuously updating log for one particular error. If the the script finds the error it should send out an email.
Thanks for all ur help (2 Replies)
Discussion started by: a12ka4
2 Replies
8. Shell Programming and Scripting
hi All,
how to find a pattern in the log file & display the above and below line
for example in the log file, i have many lines, whenever i search for "Category" it should display the above line with only few parameter like i want only the location name & department name
Thu Jul 02 11:05:23... (2 Replies)
Discussion started by: rithick256
2 Replies
9. Shell Programming and Scripting
I would like to monitor a log file using a shell script and as soon as a line with a certain string in it appears I would like to run a program. I have been playing around with doing this using tail -f, but cannot get it to work. I found something similar here:... (1 Reply)
Discussion started by: danielsbrewer
1 Replies
10. Shell Programming and Scripting
Hi there,
I have a problem here that involves bash script since I was noob in that field. Recently, I have to monitor data involve in logs so I just run command tail -f for the monitoring. The logs was generate every hour so I need to quickly change my logs every time the new hour hits according... (2 Replies)
Discussion started by: kriezo
2 Replies
rc(1M) rc(1M)
NAME
rc - general purpose sequencer invoked upon entering new run level
SYNOPSIS
DESCRIPTION
The shell script is the general sequencer invoked upon entering a new run level via the command (where N equals 0-6). The script is typi-
cally invoked by the corresponding entry in the file as follows:
is the startup and shutdown sequencer script. There is only one sequencer script and it handles all of the sequencer directories. This
script sequences the scripts in the appropriate sequencer directories in alphabetical order as defined by the shell and invokes them as
either startup or kill scripts.
If a transition from a lower to a higher run level (i.e., init state) occurs, the start scripts for the new run level and all intermediate
levels between the old and new level are executed. If a transition from a higher to a lower run level occurs, the kill scripts for the new
run level and all intermediate levels between the old and new level are executed.
If a start script link (e.g., in sequencer N has a stop action, the corresponding kill script should be placed in sequencer (e.g., Actions
started in level N should be stopped in level This way, a system shutdown (e.g., transition from level 3 directly to level 0) will result
in all subsystems being stopped.
Start and Kill Scripts
In many cases, a startup script will have both a start and a kill action. For example, the inetd script starts the Internet daemon in the
start case, and kills that process in the stop case. Instead of two separate scripts, only one exists, which accepts both the and argu-
ments and executes the correct code. In some cases, only a start action will be applicable. If this is the case, and if the action is
specified, the script should produce a usage message and exit with an error. In general, scripts should look at their arguments and pro-
duce error messages if bad arguments are present. When a script executes properly, it must exit with a return value of zero. If an error
condition exists, the return value must be nonzero.
Naming Conventions
The startup and shutdown scripts (referred to as startup scripts hereafter) exist in the directory, named after the subsystem they control.
For example, the script controls starting up the daemon. The contents of sequencer directories consist of symbolic links to startup
scripts in These symbolic links must follow a strict naming convention, as noted in the various fields of this example:
where the fields are defined as follows:
The sequencer directory is numbered to reflect the
run level for which its contents will be executed. In this case, start scripts in this directory will be executed
upon entering run level 2 from run level 1, and kill scripts will be executed upon entering run level 2 from run
level 3.
The first character of a sequencer link name determines
whether the script is executed as a start script (if the character is or as a kill script (if the character is
A three digit number is used for sequencing scripts within
the sequencer directory. Scripts are executed by type (start or kill) in alphabetical order as defined by the shell.
Although it is not recommended, two scripts may share the same sequence number.
The name of the startup script follows the sequence number.
The startup script name must be the same name as the script to which this sequencer entry is linked. In this exam-
ple, the link points to
Note that short file name systems require file names of 14 or less characters. This means that the fourth field is
limited to 10 or fewer characters.
Scripts are executed in alphabetical order. The entire file name of the script is used for alphabetical ordering
purposes.
When ordering start and kill script links, note that subsystems started in any given order should be stopped in the
reverse order to eliminate any dependencies between subsystems. This means that kill scripts will generally not have
the same numbers as their start script counterparts. For example, if two subsystems must be started in a given order
due to dependencies (e.g., followed by the kill counterparts to these scripts must be numbered so that the subsystems
are stopped in the opposite order in which they were started (e.g., followed by
Also keep in mind that kill scripts for a start script in directory will reside in For example, and might be
start/kill counterparts.
Arguments
The startup/shutdown scripts should be able to recognize the following four arguments (where applicable):
The argument is passed to scripts whose names start with Upon receiving the argument, the script should perform its start
actions.
The argument is passed to scripts whose names start with Upon receiving the argument, the script should perform its stop
actions.
The argument is passed to scripts whose names start with so that the script can report back a short message indicating
what the start action will do. For instance, when the spooler script is invoked with a argument, it echoes
This string is used by the startup routines. Scripts given just the argument will only print a message and not per-
form any actions.
The argument is passed to scripts whose names start with so that the script can report back a short message indicating
what the stop action will do. For instance, when the spooler script is invoked with a argument, it echoes
This string is used by the shutdown checklist. Scripts given just the argument will only print a message and not
perform any actions.
Script Output
To ensure proper reporting of startup events, startup scripts are required to comply with the following guidelines for script output.
o Status messages, such as
must be directed to stdout. All error messages must be directed to stderr.
o Script output, both stdout and stderr, is redirected to log file unless the startup checklist mode is set to the raw mode. In
this case, all output goes to the console. All error messages should be echoed to stdout or stderr.
o Startup scripts are not allowed to send messages directly to the console, or to start any daemons that immediately write to the
console. This restriction exists because these scripts are now started by the checklist wrapper. All script output should go to
either stdout or stderr, and thus be captured in a log file. Any console output will be garbled.
o When a startup script returns an exit code of can display a specific message on the console prior to rebooting the system. This
is achieved by creating a text file named containing the text to be displayed to the console. Note that deletes this file after
displaying the message, so startup scripts need to write this file each time a specific message is required to be displayed on
console prior to reboot.
RETURN VALUE
The return values for startup scripts are as follows:
Script exited without error.
Script encountered errors.
Script was skipped due to overriding control variables
from files, or for other reasons, and did not actually do anything.
Script will automatically reboot the system.
Script exited without error and started a process in background mode.
For return values greater than
the action is same as return value script encountered errors.
SEE ALSO
init(1M), shutdown(1M), inittab(4), rc.config(4).
rc(1M)