Date: Fri, 4 Jul 2003 14:04:44 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: "Dave [Hawk-Systems]" <dave@hawk-systems.com> Cc: freebsd-questions@freebsd.org Subject: Re: daily /security run output via periodic - stopped Message-ID: <20030704130444.GC69059@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <DBEIKNMKGOBGNDHAAKGNIENNCAAC.dave@hawk-systems.com> References: <DBEIKNMKGOBGNDHAAKGNCENMCAAC.dave@hawk-systems.com> <DBEIKNMKGOBGNDHAAKGNIENNCAAC.dave@hawk-systems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--+xNpyl7Qekk2NvDX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Jul 04, 2003 at 08:48:24AM -0400, Dave [Hawk-Systems] wrote:
> >we have 4 servers running, each sends daily and security run output emai=
l each
> >day around 3am. Recently one of them stopped sending these messages. In
> >looking at the periodic.conf and associated directories, I don't see any
> >problems or changes that I am aware of. There are no enrties in cron fo=
r it,
> >but then again there aren't any entries in the functional servers either.
> >
> >Is it possible we have disabled something by accident which could stop t=
his one
> >server from sending these messages?
>=20
> double checked everything just after sending...
>=20
> periodic.conf was missing. (doh!)
=2E.. but that's OK, as the periodic system will just run using the
default settings from /etc/defaults/periodic.conf -- note the
instructions in that file: /etc/periodic.conf should contain only
those entries you want to be different to the default values.
As for how the periodic scripts get run each night: they are run as
cron jobs, but out of the system crontab in /etc/crontab. That's a
slightly different animal which lives in a parallel universe to the
normal per-user crontabs, which are stored in /var/cron/tabs and
generally accessed via crontab(1).
As for the missing mail, did you check the client mailqueue?
# mailq -Ac
or look at the contents of /var/spool/clientmqueue. If the messages
are held up there, you should investigate what happened to the
sendmail msp queue-runner process which the system will run by default
so long as 'sendmail_enable=3DYES' or 'sendmail_enable=3DNO' is in
/etc/rc.conf.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--+xNpyl7Qekk2NvDX
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQE/BXtsdtESqEQa7a0RAgWfAJ99/ih76lYqVP/QqCOZNFfdgBpLSgCcCun9
1xvx1LfmfsRXjvmZiT3QrxI=
=i3DJ
-----END PGP SIGNATURE-----
--+xNpyl7Qekk2NvDX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030704130444.GC69059>