head	1.25;
access;
symbols
	RELENG_2_2_8_RELEASE:1.21.2.4
	RELENG_2_2_7_RELEASE:1.21.2.3
	RELENG_2_2_6_RELEASE:1.21.2.3
	RELENG_2_2_5_RELEASE:1.21.2.3
	RELENG_2_2_2_RELEASE:1.21.2.3
	RELENG_2_2_1_RELEASE:1.21.2.3
	RELENG_2_2_0_RELEASE:1.21.2.3
	RELENG_2_1_7_RELEASE:1.13.4.5
	RELENG_2_1_6_1_RELEASE:1.13.4.4
	RELENG_2_1_6_RELEASE:1.13.4.4
	RELENG_2_2:1.21.0.2
	RELENG_2_2_BP:1.21
	RELENG_2_1_5_RELEASE:1.13.4.4
	RELENG_2_1_0_RELEASE:1.13
	RELENG_2_1_0:1.13.0.4
	RELENG_2_1_0_BP:1.13
	RELENG_2_0_5_RELEASE:1.13
	RELENG_2_0_5:1.13.0.2
	RELENG_2_0_5_BP:1.13
	RELENG_2_0_5_ALPHA:1.13
	RELEASE_2_0:1.11
	BETA_2_0:1.10
	ALPHA_2_0:1.10.0.2
	MOVED_NEWCVS:1.9
	FINAL_1_1_5:1.9
	ALPHA_1_1_5:1.9
	FINAL_1_1:1.7
	GAMMA_1_1:1.7
	BETA_1_1:1.7.0.2
	BP_BETA_1_1:1.7
	FINAL_1_0:1.6
	EPSILON_1_0:1.4
	GAMMA_1_0:1.4
	BETA_1_0:1.3
	ALPHA_1_0:1.1.1.1
	V_0_0_1_0:1.1.1.1;
locks; strict;
comment	@# @;


1.25
date	97.08.13.06.12.04;	author pst;	state dead;
branches;
next	1.24;

1.24
date	97.03.10.19.18.23;	author joerg;	state Exp;
branches;
next	1.23;

1.23
date	97.03.06.10.55.46;	author joerg;	state Exp;
branches;
next	1.22;

1.22
date	97.02.08.20.54.38;	author jdp;	state Exp;
branches;
next	1.21;

1.21
date	96.10.19.21.03.23;	author alex;	state Exp;
branches
	1.21.2.1;
next	1.20;

1.20
date	96.08.07.13.35.29;	author wosch;	state Exp;
branches;
next	1.19;

1.19
date	96.06.22.13.05.19;	author joerg;	state Exp;
branches;
next	1.18;

1.18
date	96.05.22.05.43.30;	author pst;	state Exp;
branches;
next	1.17;

1.17
date	96.03.05.05.35.48;	author nate;	state Exp;
branches;
next	1.16;

1.16
date	96.01.06.22.19.35;	author ache;	state Exp;
branches;
next	1.15;

1.15
date	96.01.05.10.09.10;	author graichen;	state Exp;
branches;
next	1.14;

1.14
date	95.09.15.00.31.38;	author ache;	state Exp;
branches;
next	1.13;

1.13
date	95.05.27.01.31.38;	author ache;	state Exp;
branches
	1.13.4.1;
next	1.12;

1.12
date	95.01.05.10.15.53;	author davidg;	state Exp;
branches;
next	1.11;

1.11
date	94.11.20.23.34.51;	author ats;	state Exp;
branches;
next	1.10;

1.10
date	94.10.30.18.20.57;	author joerg;	state Exp;
branches;
next	1.9;

1.9
date	94.05.19.12.34.48;	author csgr;	state Exp;
branches;
next	1.8;

1.8
date	94.05.13.12.41.47;	author jkh;	state Exp;
branches;
next	1.7;

1.7
date	94.01.12.06.23.30;	author rgrimes;	state Exp;
branches;
next	1.6;

1.6
date	93.10.25.06.10.42;	author rgrimes;	state Exp;
branches;
next	1.5;

1.5
date	93.10.13.16.26.03;	author rgrimes;	state Exp;
branches;
next	1.4;

1.4
date	93.08.31.16.29.00;	author rgrimes;	state Exp;
branches;
next	1.3;

1.3
date	93.08.09.15.17.59;	author rgrimes;	state Exp;
branches;
next	1.2;

1.2
date	93.08.07.09.58.34;	author rgrimes;	state Exp;
branches;
next	1.1;

1.1
date	93.06.20.13.41.37;	author rgrimes;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	93.06.20.13.41.38;	author rgrimes;	state Exp;
branches;
next	;

1.13.4.1
date	96.05.22.05.44.12;	author pst;	state Exp;
branches;
next	1.13.4.2;

1.13.4.2
date	96.05.29.22.23.19;	author jkh;	state Exp;
branches;
next	1.13.4.3;

1.13.4.3
date	96.06.05.20.28.14;	author nate;	state Exp;
branches;
next	1.13.4.4;

1.13.4.4
date	96.06.25.14.56.00;	author joerg;	state Exp;
branches;
next	1.13.4.5;

1.13.4.5
date	97.02.09.02.08.35;	author jdp;	state Exp;
branches;
next	;

1.21.2.1
date	97.02.09.02.06.49;	author jdp;	state Exp;
branches;
next	1.21.2.2;

1.21.2.2
date	97.03.06.10.57.14;	author joerg;	state Exp;
branches;
next	1.21.2.3;

1.21.2.3
date	97.03.10.19.22.43;	author joerg;	state Exp;
branches;
next	1.21.2.4;

1.21.2.4
date	98.09.13.23.10.08;	author brian;	state Exp;
branches;
next	1.21.2.5;

1.21.2.5
date	99.01.01.17.44.15;	author billf;	state Exp;
branches;
next	1.21.2.6;

1.21.2.6
date	99.01.01.21.12.03;	author billf;	state Exp;
branches;
next	1.21.2.7;

1.21.2.7
date	99.09.05.11.01.56;	author peter;	state Exp;
branches;
next	;


desc
@@


1.25
log
@Make the cutover to periodic and cron.d as discussed to death on committers
for the past week.
@
text
@#!/bin/sh -
#
#	@@(#)daily	5.12 (Berkeley) 5/24/91
#
PATH=/bin:/usr/bin:/sbin:/usr/sbin
host=`hostname -s`
echo "Subject: $host daily run output"
bak=/var/backups

echo ""
echo "Removing scratch and junk files:"
if [ -d /var/preserve ]; then
	cd /var/preserve && {
	find . ! -name . -mtime +7 -exec rm -f -- {} \; ; }
fi

if [ -d /var/rwho ] ; then
	cd /var/rwho && {
	find . ! -name . -mtime +7 -exec rm -f -- {} \; ; }
fi

cd /tmp

# This is a security hole, never use 'find' on a public directory
# with -exec rm -f as root.  This can be exploited to delete any file
# on the system.
#
#find / \( ! -fstype local -o -fstype rdonly \) -a -prune -o \
#	\( -name '[#,]*' -o -name '.#*' -o -name a.out -o -name '*.core' \
#	   -o -name '*.CKP' -o -name '.emacs_[0-9]*' \) \
#		-a -atime +3 -exec rm -f -- {} \;
#
#
# The same security hole.  Purge the temp directories from unused stuff.
# Note that we must not accidentally clean the X11 lock files.
#
# Use at your own risk, but for a long-living system, this might come
# more useful than the boot-time cleaning of /tmp.  If /var/tmp and
# /tmp are symlinked together, only one of the below will actually
# run.
#
# if [ -d /tmp ]; then
# 	cd /tmp && {
# 	find . -type f -atime +3 -ctime +3 ! -name '.X*-lock' -exec rm -f -- {} \;
# 	find -d . ! -name . -type d -mtime +1 -exec rmdir -- {} \; \
# 	    >/dev/null 2>&1; }
# fi
#
# if [ -d /var/tmp ]; then
# 	cd /var/tmp && {
# 	find . ! -name . -atime +7 -ctime +3 -exec rm -f -- {} \;
# 	find -d . ! -name . -type d -mtime +1 -exec rmdir -- {} \; \
# 	    >/dev/null 2>&1; }
# fi
#
#

# remove system	messages older than 21 days
msgs -c

if [ -f /etc/news.expire ]; then
	/etc/news.expire
fi

if [ -f /var/account/acct ] ; then
	echo ""
	echo "Gathering accounting statistics:"
	cd /var/account
	if [ -f acct.2 ] ; then mv -f acct.2 acct.3 ; fi
	if [ -f acct.1 ] ; then mv -f acct.1 acct.2 ; fi
	if [ -f acct.0 ] ; then mv -f acct.0 acct.1 ; fi
	cp -pf acct acct.0
	sa -s > /dev/null
fi

echo ""
echo "Backup passwd and group files:"
if [ ! -f $bak/master.passwd.bak ] ; then
	echo "no $bak/master.passwd.bak"
	cp -p /etc/master.passwd $bak/master.passwd.bak
fi
if cmp -s $bak/master.passwd.bak /etc/master.passwd; then :; else
	echo "$host passwd diffs:"
	diff $bak/master.passwd.bak /etc/master.passwd |\
		sed 's/^\([<>] [^:]*\):[^:]*:/\1:(password):/'
	mv $bak/master.passwd.bak $bak/master.passwd.bak2
	cp -p /etc/master.passwd $bak/master.passwd.bak
fi
if [ ! -f $bak/group.bak ] ; then
	echo "no $bak/group.bak"
	cp -p /etc/group $bak/group.bak
fi
if cmp -s $bak/group.bak /etc/group; then :; else
	echo "$host group diffs:"
	diff $bak/group.bak /etc/group
	mv $bak/group.bak $bak/group.bak2
	cp -p /etc/group $bak/group.bak
fi
if [ ! -f $bak/aliases.bak ] ; then
	echo "no $bak/aliases.bak"
	cp -p /etc/aliases $bak/aliases.bak
fi
if cmp -s $bak/aliases.bak /etc/aliases; then :; else
	echo "$host aliases diffs:"
	diff $bak/aliases.bak /etc/aliases
	mv $bak/aliases.bak $bak/aliases.bak2
	cp -p /etc/aliases $bak/aliases.bak
fi
if [ -f /etc/Distfile ]; then
	if cmp -s $bak/Distfile.bak /etc/Distfile; then :; else
		mv $bak/Distfile.bak $bak/Distfile.bak2
		cp /etc/Distfile $bak/Distfile.bak
	fi
fi


# `calendar -a' needs to die. Why? Because it's a bad idea, particular
# with networked home directories, but also in general.  If you want the
# output of `calendar' mailed to you, set up a cron job to do it,
# or run it from your ~/.profile or ~/.login.
#
# echo ""
# echo "Running calendar:"
# calendar -a


if [ -d /var/spool/uucp -a -f /etc/uuclean.daily ]; then
	echo ""
	echo "Cleaning up UUCP:"
	echo /etc/uuclean.daily | su daemon
fi

echo ""
echo ""
echo "Checking subsystem status:"
echo ""
echo "disks:"
df -k -t local
echo ""
dump W
echo ""


echo ""
echo "mail:"
mailq

if [ -d /var/spool/uucp ]; then
	echo ""
	echo "uucp:"
	uustat -a
fi

echo ""
echo "network:"
netstat -i
echo ""
if [ -d /var/rwho ] ; then
	ruptime
fi

echo ""
if [ -f /etc/Distfile ]; then
	echo "Running rdist:"
	rdist -f /etc/Distfile
fi

if [ -f /etc/daily.local ]; then
    echo "Running daily.local:"
    sh /etc/daily.local
fi

sh /etc/security 2>&1 | sendmail root
@


1.24
log
@Fix a logico in my last (commented out) commit.
@
text
@@


1.23
log
@Fix the (commented out) example to prune the tree from core etc. files:
don't ever attempt to prune readonly filesystems, and properly quote
*.core against the shell.
@
text
@d28 1
a28 1
#find / ! \( -fstype local -o -fstype rdonly \) -a -prune -o \
@


1.22
log
@Security fix.  Strip the encrypted passwords out of the "master.passwd"
diff output, and replace them with "(password)".  The diffs get
mailed to root, which in many cases is forwarded across the
Internet.  A patient sniffer could acquire the entire "master.passwd"
file by saving all the diffs.  With this fix, you still see that the
password changed, but you don't see the details.

Unless somebody talks me out of it, I am going to merge this into -2.2
in 48 hours.
@
text
@d28 2
a29 2
#find / ! -fstype local -a -prune -o \
#	\( -name '[#,]*' -o -name '.#*' -o -name a.out -o -name *.core \
@


1.21
log
@If /etc/daily.local is present, run it just before the security check.
Closes PR#1822.

Submitted by:	John-Mark Gurney <jmg@@nike.efn.org> (w/some changes)
@
text
@d84 2
a85 1
	diff $bak/master.passwd.bak /etc/master.passwd
@


1.21.2.1
log
@Merge from main branch 1.21 -> 1.22: don't include encrypted passwords
in master.passwd diff output.
@
text
@d84 1
a84 2
	diff $bak/master.passwd.bak /etc/master.passwd |\
		sed 's/^\([<>] [^:]*\):[^:]*:/\1:(password):/'
@


1.21.2.2
log
@YAMFC (rev 1.23: fix the daily prune example)
@
text
@d28 2
a29 2
#find / ! \( -fstype local -o -fstype rdonly \) -a -prune -o \
#	\( -name '[#,]*' -o -name '.#*' -o -name a.out -o -name '*.core' \
@


1.21.2.3
log
@YAMFC (rev 1.24: fix a logico)
@
text
@d28 1
a28 1
#find / \( ! -fstype local -o -fstype rdonly \) -a -prune -o \
@


1.21.2.4
log
@Add Id keyword
@
text
@a2 1
#	$Id:$
@


1.21.2.5
log
@MFC: Use FQDN instead of hostname in reports (bin/9091)
@
text
@d3 1
a3 1
#	$Id: daily,v 1.21.2.4 1998/09/13 23:10:08 brian Exp $
d7 1
a7 1
host=`hostname`
@


1.21.2.6
log
@MFC: Run uucp cleanup as the uucp user (bin/7749)
@
text
@d3 1
a3 1
#	$Id: daily,v 1.21.2.5 1999/01/01 17:44:15 billf Exp $
d131 1
a131 1
	echo /etc/uuclean.daily | su -m uucp
@


1.21.2.7
log
@$Id$ -> $FreeBSD$
@
text
@d3 1
a3 1
# $FreeBSD$
@


1.20
log
@disable `calendar -a'. it's a bad idea, particular
with networked home directories

submitted by: "Boyd R. Faulkner" <faulkner@@asgard.bga.com> and
              GAWollman (long time ago)
@
text
@d167 5
@


1.19
log
@Add a few hints about the cleaning policy of /tmp, including an example
(commented out) for how to purge it regularly.
@
text
@d115 10
a124 3
echo ""
echo "Running calendar:"
calendar -a
@


1.18
log
@Eliminate warning message and add big warnings about security holes
@
text
@d33 24
@


1.17
log
@Don't try running ruptime if /var/rwho doesn't exist.
@
text
@d23 4
a26 3
# This is not safe, you need to decide what is appropriate for your
# system. Leave a warning note for now.
echo "You did not enable the cleaning of / in /etc/daily!"
@


1.16
log
@Restore broken accounting statistics:
1) It have nothing common to (new)syslog messages
2) acct.* rotating allowed only after "sa -s" run!
@
text
@d125 3
a127 1
ruptime
@


1.15
log
@changed /etc/[daily,weekly,monthly] to not rotate the logfiles by
"hand", changed /etc/crontab to call /usr/sbin/newsyslog every hour
(the entry was there before - but we haven't had any newsyslog until
today :-) and changed /etc/inetd.conf to also contain (commentet out)
entries for rpc.rquotad and rpc.sprayd (taken from NetBSD)
@
text
@d32 2
d35 1
d38 11
@


1.14
log
@If no passwd.bak/group.bak/aliases.bak exists, put warning and make them,
commands failed in old case
Produce diffs on group and aliases too
@
text
@a36 13
if [ -d /var/account ] ; then
	echo ""
	echo "Purging accounting records:"
	cd /var/account
	if [ -f acct.2 ] ; then mv -f acct.2 acct.3 ; fi
	if [ -f acct.1 ] ; then mv -f acct.1 acct.2 ; fi
	if [ -f acct.0 ] ; then mv -f acct.0 acct.1 ; fi
	if [ -f acct ] ; then
		cp -pf acct acct.0
		sa -s > /dev/null
	fi
fi

a78 17

echo ""
echo "Rotating mail log:"
cd /var/log
rm -f maillog.7
if [ -f maillog.6 ]; then mv -f maillog.6  maillog.7; fi
if [ -f maillog.5 ]; then mv -f maillog.5  maillog.6; fi
if [ -f maillog.4 ]; then mv -f maillog.4  maillog.5; fi
if [ -f maillog.3 ]; then mv -f maillog.3  maillog.4; fi
if [ -f maillog.2 ]; then mv -f maillog.2  maillog.3; fi
if [ -f maillog.1 ]; then mv -f maillog.1  maillog.2; fi
if [ -f maillog.0 ]; then mv -f maillog.0  maillog.1; fi
mv -f maillog maillog.0
cp /dev/null maillog
chmod 644    maillog
kill -1 `cat /var/run/syslog.pid`
cd /
@


1.13
log
@Use proper PATH in front of monthly
Eliminate Subject duplication for insecure output
@
text
@d52 4
d62 4
d67 2
d72 4
d77 2
@


1.13.4.1
log
@Bring in changes from head
@
text
@d23 3
a25 4

# This is a security hole, never use 'find' on a public directory
# with -exec rm -f as root.  This can be exploited to delete any file
# on the system.
@


1.13.4.2
log
@Merge from HEAD, except:

	Clients that used gnumalloc still do, despite the merge.  We're not
	bringing phkmalloc over.

	Thread stuff left out.

	PCCARD support left out.
@
text
@a32 2

# remove system	messages older than 21 days
a33 1

d38 1
a38 1
if [ -f /var/account/acct ] ; then
d40 1
a40 1
	echo "Gathering accounting statistics:"
d45 4
a48 2
	cp -pf acct acct.0
	sa -s > /dev/null
a52 4
if [ ! -f $bak/master.passwd.bak ] ; then
	echo "no $bak/master.passwd.bak"
	cp -p /etc/master.passwd $bak/master.passwd.bak
fi
a58 4
if [ ! -f $bak/group.bak ] ; then
	echo "no $bak/group.bak"
	cp -p /etc/group $bak/group.bak
fi
a59 2
	echo "$host group diffs:"
	diff $bak/group.bak /etc/group
a62 4
if [ ! -f $bak/aliases.bak ] ; then
	echo "no $bak/aliases.bak"
	cp -p /etc/aliases $bak/aliases.bak
fi
a63 2
	echo "$host aliases diffs:"
	diff $bak/aliases.bak /etc/aliases
d78 17
d126 1
a126 3
if [ -d /var/rwho ] ; then
	ruptime
fi
@


1.13.4.3
log
@Mega-commit cleanup.  Don't use newsyslog(8) for logfile rotations since
it doesn't exist in -stable, so revert to using the old methods.
@
text
@d34 1
a34 1
# remove system messages older than 21 days
a93 17

echo ""
echo "Rotating mail log:"
cd /var/log
rm -f maillog.7
if [ -f maillog.6 ]; then mv -f maillog.6  maillog.7; fi
if [ -f maillog.5 ]; then mv -f maillog.5  maillog.6; fi
if [ -f maillog.4 ]; then mv -f maillog.4  maillog.5; fi
if [ -f maillog.3 ]; then mv -f maillog.3  maillog.4; fi
if [ -f maillog.2 ]; then mv -f maillog.2  maillog.3; fi
if [ -f maillog.1 ]; then mv -f maillog.1  maillog.2; fi
if [ -f maillog.0 ]; then mv -f maillog.0  maillog.1; fi
mv -f maillog maillog.0
cp /dev/null maillog
chmod 644    maillog
kill -1 `cat /var/run/syslog.pid`
cd /
@


1.13.4.4
log
@Merge the changes from rev 1.19 of /etc/daily and 1.92 of /etc/rc --
Hint about alternatives to the boot-time cleanup of /tmp
@
text
@a32 24
#
# The same security hole.  Purge the temp directories from unused stuff.
# Note that we must not accidentally clean the X11 lock files.
#
# Use at your own risk, but for a long-living system, this might come
# more useful than the boot-time cleaning of /tmp.  If /var/tmp and
# /tmp are symlinked together, only one of the below will actually
# run.
#
# if [ -d /tmp ]; then
# 	cd /tmp && {
# 	find . -type f -atime +3 -ctime +3 ! -name '.X*-lock' -exec rm -f -- {} \;
# 	find -d . ! -name . -type d -mtime +1 -exec rmdir -- {} \; \
# 	    >/dev/null 2>&1; }
# fi
#
# if [ -d /var/tmp ]; then
# 	cd /var/tmp && {
# 	find . ! -name . -atime +7 -ctime +3 -exec rm -f -- {} \;
# 	find -d . ! -name . -type d -mtime +1 -exec rmdir -- {} \; \
# 	    >/dev/null 2>&1; }
# fi
#
#
@


1.13.4.5
log
@Merge from main branch 1.21 -> 1.22: don't include encrypted passwords
in master.passwd diff output.
@
text
@d84 1
a84 2
	diff $bak/master.passwd.bak /etc/master.passwd |\
		sed 's/^\([<>] [^:]*\):[^:]*:/\1:(password):/'
@


1.12
log
@Removed daily rm'ing of files in /tmp, /var/tmp, and /scratch. There is no
safe way to do this, and envites very unpleasant results. Removed fsck'ing
of all the disks on the system as it provides output that is almost always
meaningless and only envites bug reports.

Reviewed by:	Jordan Hubbard
@
text
@d5 1
a5 1
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local
d133 1
a133 1
sh /etc/security 2>&1 | mail -s "daily insecurity output" root
@


1.11
log
@Submitted by:	Julian H. Stacey
Changed the echo to match correctly the intended code.
@
text
@a11 23
if [ -d /tmp ]; then
	cd /tmp && {
	find . -type f -atime +3 -exec rm -f -- {} \;
	find . ! -name . -type d -mtime +1 -exec rmdir -- {} \; \
	    >/dev/null 2>&1; }
fi

if [ -d /var/tmp ]; then
	cd /var/tmp && {
	find . ! -name . -atime +7 -exec rm -f -- {} \;
	find . ! -name . -type d -mtime +1 -exec rmdir -- {} \; \
	    >/dev/null 2>&1; }
fi

if [ -d /scratch ]; then
	cd /scratch && {
	find . ! -name . ! -fstype local -a -prune -o \
		-atime +1 -exec rm -f -- {} \;
	find . ! -name . ! -fstype local -a -prune -o \
		-type d -mtime +1 -exec rmdir -- {} \; \
	    >/dev/null 2>&1; }
fi

a125 4

echo ""
echo "Checking filesystems:"
fsck -n | grep -v '^\*\* Phase'
@


1.10
log
@daily:
	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.
@
text
@d48 1
a48 1
echo "You did not enable the cleaning of /tmp in /etc/daily!"
@


1.9
log
@Turn on purging of accounting records in /etc/daily.
(Now that we have sa)
@
text
@d47 2
a48 1
# system.
d51 1
a51 1
#	\( -name '[#,]*' -o -name '.#*' -o -name a.out -o -name core \
d128 1
a128 1
df -k
@


1.8
log
@From: Heikki Suonsivu <hsu@@clinet.fi>

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?
@
text
@d59 12
a70 7
#echo ""
#echo "Purging accounting records:"
#mv /var/account/acct.2 /var/account/acct.3
#mv /var/account/acct.1 /var/account/acct.2
#mv /var/account/acct.0 /var/account/acct.1
#cp /var/account/acct /var/account/acct.0
#sa -s > /dev/null
@


1.7
log
@Commented out the global clean up that searched all file systems and
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
@
text
@d28 4
a31 2
	find . ! -name . -atime +1 -exec rm -f -- {} \;
	find . ! -name . -type d -mtime +1 -exec rmdir -- {} \; \
@


1.6
log
@Redirect standard error onto standard out when call /etc/security so
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
@
text
@d44 8
a51 4
find / ! -fstype local -a -prune -o \
	\( -name '[#,]*' -o -name '.#*' -o -name a.out -o -name core \
	   -o -name '*.CKP' -o -name '.emacs_[0-9]*' \) \
		-a -atime +3 -exec rm -f -- {} \;
@


1.5
log
@Change uusnap to uustat -a, since we do not have a uusnap installed (some
one did not finish porting uucp/contrib directory)
@
text
@d148 1
a148 1
sh /etc/security | mail -s "daily insecurity output" root
@


1.4
log
@Reenabled rotation of log files and killing of syslogd now that the
lockup problem is fixed.
@
text
@d129 1
a129 1
	uusnap
@


1.3
log
@Due to the bug with the console drivers and kill syslogd I have disabled that
in the daily and weekly scripts so that we don't get bug reports about
something we already know.  There are explanory comments in the files.
@
text
@d88 16
a103 20
# Due to a console sub system bug doing the kill -1 of syslogd
# will lock up the console.  This has been disabled until that
# is fixed.
#
#echo ""
#echo "Rotating mail log:"
#cd /var/log
#rm -f maillog.7
#if [ -f maillog.6 ]; then mv -f maillog.6  maillog.7; fi
#if [ -f maillog.5 ]; then mv -f maillog.5  maillog.6; fi
#if [ -f maillog.4 ]; then mv -f maillog.4  maillog.5; fi
#if [ -f maillog.3 ]; then mv -f maillog.3  maillog.4; fi
#if [ -f maillog.2 ]; then mv -f maillog.2  maillog.3; fi
#if [ -f maillog.1 ]; then mv -f maillog.1  maillog.2; fi
#if [ -f maillog.0 ]; then mv -f maillog.0  maillog.1; fi
#mv -f maillog maillog.0
#cp /dev/null maillog
#chmod 644    maillog
#kill -1 `cat /var/run/syslog.pid`
#cd /
@


1.2
log
@Fixed daily so that it no longer does accounting since FreeBSD does not
yet have the accounting stuff in it.  Disabled ncheck search in security
due to missing ncheck.
@
text
@d88 20
a107 16
echo ""
echo "Rotating mail log:"
cd /var/log
rm -f maillog.7
if [ -f maillog.6 ]; then mv -f maillog.6  maillog.7; fi
if [ -f maillog.5 ]; then mv -f maillog.5  maillog.6; fi
if [ -f maillog.4 ]; then mv -f maillog.4  maillog.5; fi
if [ -f maillog.3 ]; then mv -f maillog.3  maillog.4; fi
if [ -f maillog.2 ]; then mv -f maillog.2  maillog.3; fi
if [ -f maillog.1 ]; then mv -f maillog.1  maillog.2; fi
if [ -f maillog.0 ]; then mv -f maillog.0  maillog.1; fi
mv -f maillog maillog.0
cp /dev/null maillog
chmod 644    maillog
kill -1 `cat /var/run/syslog.pid`
cd /
@


1.1
log
@Initial revision
@
text
@d53 7
a59 7
echo ""
echo "Purging accounting records:"
mv /var/account/acct.2 /var/account/acct.3
mv /var/account/acct.1 /var/account/acct.2
mv /var/account/acct.0 /var/account/acct.1
cp /var/account/acct /var/account/acct.0
sa -s > /dev/null
@


1.1.1.1
log
@Initial import of 386BSD 0.1 othersrc/etc
@
text
@@
