Leave a warning to the sysop if (s)he didn't yet
enable the /tmp cleanup code.
Made `core' in the cleanup template look `*.core'.
Replace `df -k' by `df -k -t local', since the stats
for kernfs, procfs etc. are not of much interest, and
the inclusion of nfs systems might hang the machine (nor is it a
`disk' statistic as the headline's telling).
weekly:
Modified the locate.updatedb part to work even if there's no
database yet; report errors other than `Permission denied' instead
of silently ignoring all of them.
Added functionality to rebuild the whatis database once a week.
FreeBSD release still nukes everything on scratch using a big-hammer
method, even if it is nfs-mounted (and, when it is, the expiration policy
may be different). Daily script should by default do nothing to remote
filesystems?
added a note that you must decide what is appropriate for your system.
>From: borsburn@mcs.kent.edu (Bret Orsburn)
Date: Wed, 12 Jan 94 01:09:43 -0500
I've finally figured out (one of the reasons) why I can't run MS-Windows
after running FreeBSD 1.0...*sometimes*.
Here's your first clue. This is what your MS-Windows video drivers are called
if you run a Number 9 GXE video card:
/dos/windows/system/#9gxetc.drv
/dos/windows/system/#9gxe.drv
that the errors from /etc/security are in the mail message from
/etc/security and not the /etc/daily mail message. Now just to fix
the bug in /etc/security
