| From: Tim <ignored_mailbox@xxxxxxxxxxxx> | On Wed, 2008-02-13 at 22:02 -0500, Joe(theWordy)Philbrook wrote: | > At the moment however I've found that commenting out everything in the | > puplet script combined with eliminating all the yum-updatesd links | > from /etc/rc.d/rc*.d. has solved the problem (at least for now) If | > some future yum update run should restore those to running condition | > I'll have to remember to test that save button before redoing my | > 'fix' | | Simply run: | | yum remove yum-updatesd | | And get rid of it, if you're not going to use it. Puplet won't do | anything without it, and you don't need it for manual updating. The old fashioned Red Hat way of changing what things are started at starup is chkconfig. $ /sbin/chkconfig --list | grep yum yum-updatesd 0:off 1:off 2:off 3:on 4:on 5:on 6:off Suggested command (untested): # /sbin/chkconfig yum-updatesd off That only affects future boots. To affect the running system: # /sbin/service yum-updatesd stop
