Sponsored Content
Full Discussion: Monitor via crontab
Top Forums Shell Programming and Scripting Monitor via crontab Post 302262851 by mirusnet on Saturday 29th of November 2008 06:37:55 AM
Old 11-29-2008
Where is the problem?
Just add in second cron script something like:

kill `ps auxww | grep 'your first cron task' | do some awk`
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Monitor wont come on...

I know this may not be the right forum, but here goes. Last night I was playing my favorite game Everquest and my monitor goes blank... I was able to save out of my game and shut it down... My question is this: I thought my monitor had died but this morning I was able to get it to come back... (6 Replies)
Discussion started by: Kelam_Magnus
6 Replies

2. Solaris

PC monitor

In order to use a regular PC monitor would I need to do any configuration changes to my Ultra 5 box running Solaris 8 ? (1 Reply)
Discussion started by: mangolinux
1 Replies

3. Shell Programming and Scripting

Monitor File Changes

I am trying to monitor a log file and kick of a script when a change occurs. I know I could do this with a cron job and check for differences at set intervals, but I need the script to be dynamic and notify me as soon as there is a change in the log file. If anyone knows of a way to do this please... (1 Reply)
Discussion started by: goreb13
1 Replies

4. UNIX for Dummies Questions & Answers

Looking for monitor/top

I'm new to SUN (SunOS 5.8) and I can't find any monitoring tools to check cpu, memory, disk ... performance. Previously on unix servers I have used 'top' & 'monitor' but these commands are not on the box on in the man pages. Anyone suggest equivalent commands? (1 Reply)
Discussion started by: pavelmac
1 Replies

5. Shell Programming and Scripting

Monitor: Read from the monitor

Hello, I would like to write a script that use the display as an input. In the display there is a list of file. I want to use it as an array and this would be the input in my script. Does somebody know how do I make it? (2 Replies)
Discussion started by: mig8
2 Replies

6. Shell Programming and Scripting

Help with HD monitor script

Hi, I'm new to linux and I'm trying to compile a hard drive monitoring script. I've seen a few on the internet and I've attempted to stumble through but I'm stuck at my while/do scenario. I assigned the variable NUM then took the percentage from my output and cut the % so it would be just a... (6 Replies)
Discussion started by: crocyson
6 Replies

7. Hardware

Fedora 16 dual monitor - dual head - automatic monitor shutdown

Hi, I am experiencing troubles with dual monitors in fedora 16. During boot time both monitors are working, but when system starts one monitor automatically shut down. It happend out of the blue. Some time before when I updated system this happend but then I booted older kernel release and... (0 Replies)
Discussion started by: wakatana
0 Replies

8. Shell Programming and Scripting

Monitor Website

Hi all, i need to do the following, when i connect to my website it prints out "Welcome User", but sometimes there are errors like "dictionary not loaded" or "wrong user name or password" so i wanted to make a script that checks that login page, and if i get the Welcome massage do nothing,... (6 Replies)
Discussion started by: charli1
6 Replies

9. Infrastructure Monitoring

Searching for Saas Monitor service which monitor my servers which are sitting in different providers

Sorry if this is the wrong forum Searching for Saas Monitor service which monitor my servers which are sitting in different providers . This monitor tool will take as less CPU as possible , and will send info about the server to main Dashboard. The info I need is CPU / RAM / my servers status (... (1 Reply)
Discussion started by: umen
1 Replies
CRONTAB(1)						    BSD General Commands Manual 						CRONTAB(1)

NAME
crontab -- maintain crontab files for individual users (ISC Cron V4.1) SYNOPSIS
crontab [-u user] crontab [-elr] DESCRIPTION
crontab is the program used to install, deinstall, or list the tables used to drive the cron(8) daemon in ISC Cron. Each user can have their own crontab, and though these are files in /var/cron, they are not intended to be edited directly. If the /var/cron/allow file exists, then you must be listed therein in order to be allowed to use this command. If the /var/cron/allow file does not exist but the /var/cron/deny file does exist, then you must not be listed in the /var/cron/deny file in order to use this command. If neither of these files exists, depending on the compiled in settings, only the super user will be allowed to use this command, or everyone will be allowed to use this command. On NetBSD everyone is allowed to use this command. The default maximum size for a crontab is 256 kilobytes, but this may be changed for all users on the system by putting the desired maximum size (in bytes) in the /var/cron/maxtabsize file. If the -u option is given, it specifies the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e., the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you should always use the -u option for safety's sake. The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is given. The -l option causes the current crontab to be displayed on standard output. The -r option causes the current crontab to be removed. The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit from the editor, the modified crontab will be installed automatically. FILES
/var/cron/allow Optional list of users that are allowed to use crontab. /var/cron/deny Optional list of users that are disallowed to use crontab. /var/cron/maxtabsize Maximum size of crontab files. Defaults to 256 kilobytes. /var/cron/tabs/ Directory containing the individual user crontab files, named after the user. DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line. SEE ALSO
crontab(5), cron(8) STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). This new command syntax differs from previous versions of Vixie Cron, as well as from the classic Version 3 AT&T UNIX syntax. AUTHORS
Paul Vixie <vixie@isc.org> BSD
May 6, 2010 BSD
All times are GMT -4. The time now is 12:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy