Xref: utzoo unix-pc.general:3593 comp.sys.att:7339
Path: utzoo!attcan!telly!moore!ziebmef!cks
From: cks@ziebmef.uucp (Chris Siebenmann)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: yet again Re: crontab Daemon-from-Hell
Message-ID: <1989Aug18.012625.28798@ziebmef.uucp>
Date: 18 Aug 89 05:26:24 GMT
References: <19071@cup.portal.com> <14373@bfmny0.UUCP> <19196@cup.portal.com> <1545@sialis.mn.org> <1212@cbnewsc.ATT.COM> <27606@pbhya.PacBell.COM> <19560@cup.portal.com>
Organization: Ziebmef Public Access Unix, Toronto, Ontario
Lines: 26

thad@cup.portal.com (Thad P Floryan) writes (in a really ancient
 article I should have replied to long ago):
| From my displays at the West Coast Computer Faire, discussions in the local
| UNIXPC SIG of the AT&T Users' Group, and from other chance meetings of fellow
| UNIXPC'ers, it's clear to me that MOST owners/users of UNIXPC systems are
| simply not aware of such things being done TO them (by the crontab scripts and
| whatever else.)

 Congratulations; you've just learned another lesson of Unix system
administraion. One should *always* look at the automated scripts that
ye spiffy Unix system wants to run; from crontab, on startup, in
/etc/profile, in /etc/inittab. One usually finds out some quite
interesting and often important information, and one avoids nasty
surprises (like that fsck -y that's probably *still* in people's
/etc/rc; send email for a copy of my article about why this is a Real
Bad Idea and how to fix it).

[For example, take a look at /etc/cleanup.wk -- it shows you how to
 get smgr to empty out /usr/adm/cronlog, for example (and it removes
 week-old core files for you, and other functions).]
-- 
"Would that Aza Chorn had teleported Bates elsewhere and not removed
 so charming and preposterous a folly from our skyline ... but then he
 could not have known, not being raised around these parts."
Chris Siebenmann		uunet!{utgpu!moore,attcan!telly}!ziebmef!cks
cks@ziebmef.UUCP	     or	.....!utgpu!{,ontmoh!,ncrcan!brambo!}cks