Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!allegra!mp
From: mp@allegra.UUCP
Newsgroups: comp.unix.questions
Subject: Re: How to make sendmail re-read the configuration file (and cron)
Message-ID: <6437@allegra.UUCP>
Date: Sun, 25-Jan-87 20:31:27 EST
Article-I.D.: allegra.6437
Posted: Sun Jan 25 20:31:27 1987
Date-Received: Mon, 26-Jan-87 06:37:44 EST
References: <136@quacky.mips.UUCP> <201@devon.UUCP> <2409@mcc-pp.UUCP> <5128@mimsy.UUCP>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 19

As for the original question, the folks at ulysses run /usr/lib/sendmail -bs
from inetd.  You then need to put calls to /usr/lib/sendmail -q
in crontab, but this isn't such a bad idea anyway, since for some
reason it results in far fewer hung sendmail processes compared to
sendmail -bd -qxxxm.

As for ables@mcc-pp's question about cron not noticing changes in a
shared crontab, I think the problem may be due to the caching in ND.
(I'm presuming that the shared copy is in /pub, not in an NFS
partition; we have the same problem with our shared /usr/lib/aliases,
which lives in ND rather than NFS so that we can control access to
it).  Modifying cron so it doesn't keep /usr/lib/crontab open all the
time, and periodically flushing the clients' disk caches should help.
We've found "du /pub" - we have several thousand files in our /pub -
and a couple "umount /pub"'s (umount will fail, of course,
but it does what we want) usually flush the cache.

	Mark Plotnick
	allegra!mp