Tim Evans wrote:
> I have a newly installed RHEL5 system, on which yum-updatesd is acting
> strangely. At boot time, or anytime the service is started, or re-started, the
> service connects (/var/log/up2date shows the connect).
>
> One hour later, it connects again.
>
> After that, it never connects again unless the service is stopped and restarted.
>

It happens I have a newly installed (a few hours ago) CentOS5 system.

There is no /var/log/up2date, and I don't expect one on your system or
mine, yum is the tool on RHEL5.


yum-updatesd is logging to facility daemon, I checked by inspecting the
code with vim. However, on my system syslogd is not configured to log
"daemon" messages anywhere, which I find a bit odd. Check your
/etc/syslog.conf - it might explain your /var/log/up2date.

I've added a line to /etc/syslog.conf but it's too early to tell what
yum-updatesd is doing, if anything. It's not actually configured (on my
system) to be very useful.

Here's my extra line:
[root@(protected)
daemon.*           /var/log/daemon.log
[root@(protected) ~]#

More usual is something like
daemon.info           /var/log/daemon.log
but I note all the other lines are logging all.




--

Cheers
John

-- spambait
1aaaaaaa@(protected)
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

_______________________________________________
rhelv5-list mailing list
rhelv5-list@(protected)
https://www.redhat.com/mailman/listinfo/rhelv5-list