Joseph A Nagy Jr said:
Joseph A Nagy Jr wrote:
Is there any way to completely and totally prevent the rhnd from working? Even though I've stopped and unchecked it in the services conf screen, I still get crond messages letting me know of up2date's results!
Date: Fri, 20 Jun 2003 01:07:01 -0500 From: root <root@xxxxxxxxxxxxxxxxxxxxx> To: root@xxxxxxxxxxxxxxxxxxxxx Subject: LogWatch for localhost.localdomain
################### LogWatch 4.3.1 (01/13/03) ####################
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [snip]
--------------------- up2date Begin ------------------------
**Unmatched Entries** [Sun Jun 15 04:48:49 2003] up2date updating login info
[snip]
[Tue Jun 17 08:35:05 2003] up2date successfully retrieved authentication token from up2date server [Tue Jun 17 08:35:55 2003] up2date availablePackageList from network [Tue Jun 17 08:36:31 2003] up2date solving dep for: ['libdb.so.2', 'libdb.so.2', 'libdb.so.2', 'libdb.so.2(GLIBC_2.0)', 'libdb.so.2', 'libdb.so.2', 'libdb.so.2']
---------------------- up2date End ------------------------- ###################### LogWatch End #########################
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Let me try again, just like I said yesterday:
The mails are sent by logwatch [see where it says LogWatch twice in that e-mail?], so you probably want to look at it's config in /etc/log.d/logwatch.conf.
The reason you are still getting info about up2date might also be related to bug 80496: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=80496 [Notice the dates and how they are for Jun 15-Jun 17, but nothing after that?]
Yeah, I did notice that. I also didn't have a logwatch.spec file until now.
--
Wielder of the mighty +1 LARTsaber of Unsubscribe Instructions At End of Message,
the +3 Clue-by-Four of No Attachments to a Mailing List,
and the -4 Shield of No Spell Checker
