August 16, 2007, at 11:39 PM by removed false wikilinks--
Changed lines 10-11 from:
# mv /usr/sbin/CheckDiskFull /usr/sbin/CheckDiskFull_NOhrlyBeeps
Changed lines 14-15 from:
# mv /share/hdd/data/usr/sbin/CheckDiskFull /share/hdd/data/usr/sbin/CheckDiskFull_NOhrlyBeeps
Changed lines 18-19 from:
# ln -s /usr/sbin/CheckDiskFull /share/hdd/data/NOhrlyBeeps
August 16, 2007, at 07:14 PM by Added info about crontab--
Added lines 29-31:
If you have a sane EDITOR variable with a full path to a suitable editor, the command "crontab -e" will edit the crontab file with it, and then when the editor is closed and the file saved out, the crontab daemon will be informed.
January 27, 2006, at 12:27 PM by Rename CheckDiskFull--
Added lines 4-28:
Rename the program doing the beeping
It's a cron job (a line in /etc/crontab). If you don't want to learn about them, just rename the file Linux will try to execute, and it can't happen. Just like in Windows.
(Or, after all future reboots)
I like to put in a very visible reminder when I've mucked with something:
BTW, you do want to know when your HDD is nearly full because IF it gets full, *nixes get unhappy, and when they're unhappy, their users are unhappy.
I turned it off because it's warning that a 300Gb drive only has 2% of space left. That's 6 Gb, and that's 256 times larger than my first HDD . I've stopped writing to the drive (I write to the 2nd instead) so I leave it for Linux's use.
Just stop beeping me about it.
When I get ambitious, I'll edit the crontab (after reading up on it of course), and put in my own check (for something like 700M left?). You can't just edit the file; you have to inform the running "cron daemon" that things have changed. So I'll read. --cz
August 22, 2005, at 03:31 PM by--
Added lines 1-3:
Why does my NSLU2 beep every eight hours?
peecock41 figured out what it means when the NSLU2 beeps every 8 hours.