10-19-2013
rm -r is an old chestnut.
ifconfig -a 1 has a surprising impact - at least on Solaris.
Also good on Unix: crontab. Hanging. Now don't terminate with ^D, this will wipe the crontab. Dito with ^C on some buggy implementations.
This User Gave Thanks to MadeInGermany For This Post:
4 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i found some load rules in our unix script.any know about it>? (1 Reply)
Discussion started by: Diddy
1 Replies
2. What is on Your Mind?
I you haven't already see it yet, I just wanted to share with you the following video :
How lobbies controls international organizations regarding Food/Health ...
Dailymotion - NWO - Nouvel Ordre Mondial - Codex Alimentarius - Food Plan - une vidéo News & Politics
What happen when fees come... (2 Replies)
Discussion started by: ctsgnb
2 Replies
3. Windows & DOS: Issues & Discussions
I have a Excel VBA script that automatically runs when opened, extracts one table from a Microsoft Access Database, saves it as CSV, closes it, extracts another, saves it as CSV, closes it, then terminates itself.
Is is called from a short .bat file using the /e option so that Excel does not... (1 Reply)
Discussion started by: Michael Stora
1 Replies
4. What is on Your Mind?
NSA Starts Contributing Low-Level Code to UEFI BIOS Alternative (0 Replies)
Discussion started by: wisecracker
0 Replies
CRON(8) System Manager's Manual CRON(8)
NAME
cron - daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d/ directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
SEE ALSO
crontab(1), crontab(5)
AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 20 December 1993 CRON(8)