On Mon, 2006-10-23 at 04:04 -0700, root wrote: Questions below: > Oct 22 04:10:02 bastion sendmail: sendmail -HUP succeeded > Oct 22 04:10:02 bastion sendmail: sendmail -HUP succeeded > Oct 22 04:10:02 bastion sendmail: sm-client -HUP succeeded > Oct 22 04:10:02 bastion sendmail: sm-client -HUP succeeded > Oct 22 05:10:02 bastion sendmail: sendmail -HUP succeeded > Oct 22 05:10:02 bastion sendmail: sendmail -HUP succeeded > Oct 22 05:10:02 bastion sendmail: sm-client -HUP succeeded > Oct 22 05:10:02 bastion sendmail: sm-client -HUP succeeded Why is sendmail being restarted every hour on bastion? Better yet, why is it running sendmail? > Oct 22 05:11:49 cvs-int rhnsd[10625]: running program /usr/sbin/rhn_check > Oct 22 05:15:19 proxy4 rhnsd[1224]: running program /usr/sbin/rhn_check > Oct 22 05:17:16 proxy2 rhnsd[12819]: running program /usr/sbin/rhn_check > Oct 22 05:44:57 proxy1 rhnsd[1686]: running program /usr/sbin/rhn_check > Oct 22 05:45:19 proxy4 rhnsd[1227]: running program /usr/sbin/rhn_check > Oct 22 05:56:50 cvs-int rhnsd[11010]: running program /usr/sbin/rhn_check > Oct 22 06:00:18 db1 rhnsd[5452]: running program /usr/sbin/rhn_check > Oct 22 06:01:17 bastion rhnsd[11168]: running program /usr/sbin/rhn_check > Oct 22 06:02:14 proxy3 rhnsd[27507]: running program /usr/sbin/rhn_check > Oct 22 06:05:38 app2 rhnsd[4430]: running program /usr/sbin/rhn_check I can think of something to add to the epylog weed list, can you? :) -sv