04-04-2016
Sure gull04.
I will go through this link.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am the Linux Admin in my organisation and need to write a shell script which will monitor the machine statistics every day and will send a consolidated report to me on my email id / will display the output into a file.
Does anyone have such kind of script fulfilling this kind of purpose?
... (4 Replies)
Discussion started by: csaha
4 Replies
2. Shell Programming and Scripting
HI,
I'm new in unix. I would like to know if you have a ready script for monitoring the weblogic and managed servers. I want to have a script that checks the weblogic once in a while if it's up and running. if not running, will send an email to me. any idea?
please help me. i will... (4 Replies)
Discussion started by: tungaw2004
4 Replies
3. Shell Programming and Scripting
hi friends,
I am trying to automate the daily monitoring process of UNIX server and it's processes. the script are below
i executed the above script using ksh -x monitortest1.sh in root login . It shows error at some lines .
1. i logged in using root ,but it... (8 Replies)
Discussion started by: rdhaprakasam
8 Replies
4. Shell Programming and Scripting
hi I need a shell script which runs perpetually in background and monitors different aspects of different users on different files and their usages
for example say there r 3 users
so i want when they log in i.e. their log in time and their file access, modify and change log of each file of a... (3 Replies)
Discussion started by: rrd1986
3 Replies
5. Shell Programming and Scripting
Hi,
need help to write one shell script to monitor UNIX file systems and if any changes happend like deletion of any file, adding new file, time stamp changed, permisson changed etc. Script need to send alert mail to defined person/mail id.
I request someone to help me to create the... (1 Reply)
Discussion started by: vjauhari
1 Replies
6. Shell Programming and Scripting
Hello Forum,
I have prepared script to monitor the tomcat status. Following is the script which will monitor tomcat instance.I need little modifcation in the script. My script will grep for java,the output of grep command will analyze by if condition under for loop and will
send following echo... (7 Replies)
Discussion started by: coolguyamy
7 Replies
7. Red Hat
Hi all,
-------------------------
Linux OS Version/Release:
-------------------------
Red Hat Enterprise Linux Server release 5.5 (Tikanga)
Linux <hostname> 2.6.18-194.8.1.el5 #1 SMP Wed Jun 23 10:52:51 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
I have a server that hosts 30+ Oracle... (1 Reply)
Discussion started by: newbie_01
1 Replies
8. Shell Programming and Scripting
Im having a bit of troble coming up with a script that does this monitors processes to see if they die, if they do die, restart the process
and write out to a log file that the process was restarted with the new PID and the date and time the new process was launched.
Any suggestions? (1 Reply)
Discussion started by: jspinal
1 Replies
9. Shell Programming and Scripting
Hello Forum,
I have prepared script to monitor the tomcat status.
Following is the script which will monitor tomcat instance.
I need little modifcation in the script.
My script will grep for process,
the output of grep command will analyze by if condition under for loop and will send... (2 Replies)
Discussion started by: ooilinlove
2 Replies
10. Shell Programming and Scripting
Hi guys,
I didn't understand this monitoring script request - I don't ask for the script result.
If you understand the request, I'm just asking an explanation to simplify it for me.
THE Script Request:
Our organization keeps various files in directories structured as... (2 Replies)
Discussion started by: moshesa
2 Replies
AT(1) General Commands Manual AT(1)
NAME
at - execute commands at a later time
SYNOPSIS
at [ -c ] [ -s ] [ -m ] time [ day ] [ file ]
DESCRIPTION
At spools away a copy of the named file to be used as input to sh(1) or csh(1). If the -c flag (for (csh(1))) or the -s flag (for (sh(1)))
is specified, then that shell will be used to execute the job; if no shell is specified, the current environment shell is used. If no file
name is specified, at prompts for commands from standard input until a ^D is typed.
If the -m flag is specified, mail will be sent to the user after the job has been run. If errors occur during execution of the job, then a
copy of the error diagnostics will be sent to the user. If no errors occur, then a short message is sent informing the user that no errors
occurred.
The format of the spool file is as follows: A four line header that includes the owner of the job, the name of the job, the shell used to
run the job, and whether mail will be set after the job is executed. The header is followed by a cd command to the current directory and a
umask command to set the modes on any files created by the job. Then at copies all relevant environment variables to the spool file. When
the script is run, it uses the user and group ID of the creator of the spool file.
The time is 1 to 4 digits, with an optional following `A', `P', `N' or `M' for AM, PM, noon or midnight. One and two digit numbers are
taken to be hours, three and four digits to be hours and minutes. If no letters follow the digits, a 24 hour clock time is understood.
The optional day is either (1) a month name followed by a day number, or (2) a day of the week; if the word `week' follows, invocation is
moved seven days further off. Names of months and days may be recognizably truncated. Examples of legitimate commands are
at 8am jan 24
at -c -m 1530 fr week
at -s -m 1200n week
At programs are executed by periodic execution of the command /usr/libexec/atrun from cron(8). The granularity of at depends upon the how
often atrun is executed.
Error output is lost unless redirected or the -m flag is requested, in which case a copy of the errors is sent to the user via mail(1).
FILES
/usr/spool/at spooling area
/usr/spool/at/yy.ddd.hhhh.* job file
/usr/spool/at/past directory where jobs are executed from
/usr/spool/at/lasttimedone last time atrun was run
/usr/libexec/atrun executor (run by cron(8))
SEE ALSO
atq(1), atrm(1), calendar(1), sleep(1), cron(8)
DIAGNOSTICS
Complains about various syntax errors and times out of range.
BUGS
Due to the granularity of the execution of /usr/libexec/atrun, there may be bugs in scheduling things almost exactly 24 hours into the
future.
If the system crashes, mail is not sent to the user informing them that the job was not completed.
Sometimes old spool files are not removed from the directory /usr/spool/at/past. This is usually due to a system crash, and requires that
they be removed by hand.
4th Berkeley Distribution October 21, 1996 AT(1)