[CentOS] Two small issues after upgrade to 4.2

Kai Schaetzl maillists at conactive.com
Mon Oct 24 12:40:24 UTC 2005


I made a yum update to 4.2 yesterday. The first "major" update I did on 
CentOS, I'm only using it for a few weeks now, starting with 4.1. Mainly 
for evaluation for a prospected migration from Suse to CentOS. Basically 
the update went very well, fast (only 180 MB needed to be installed) and 
smooth. But there were two small issues where I don't know why they 
happened:

1. There was a (actually two) spamassassin.rpm of SA 3.1.0 installed, the 
rpm was built from the tar.gz sources for SA with the specs file provided 
with it. It produces two files for installation: perl-Mail-SpamAssassin 
and spamassassin. The update wiped them and installed SA 3.0.4 with this 
message:
Obsoleting: perl-Mail-SpamAssassin.i386 0:3.1.0-1 with spamassassin.i386 
0:3.0.4-1.el4

Shouldn't this update get skipped because the version information is 
higher than the CentOS package? I found several mentions that I can 
exclude packages from yum updating. How can I do this? I don't want to 
update only specific packages, I only want to exclude a very few packages.

2. sshd seems to start twice or so since that update. No problems with 
ssh, though.

from boot.log:
Oct 24 14:00:16 nx05 sshd:  succeeded

from warn log:
Oct 24 14:00:16 nx05 sshd[1737]: error: Bind to port 22 on 0.0.0.0 failed: 
Address already in use.

Same thing happens when I restart sshd and even when I reload it.
There was a new sshd_config installed, I think I read something about 
removing ssh 1 protocol from it. This can't be the cause. There's only one 
instance of sshd running apart from the children for actual logins.
Why is this happening, how to fix it?

There is another question that arises in this context: will a yum update 
always overwrite with new configuration files, if that file got changed 
from the originally installed one? I'm used from Suse that new 
configuration files get saved with another extension if the original file 
got changed or in some cases it overwrites the file but copies the old 
file to a backup. I can also expressly exclude some config files from 
overwriting via sysconfig (if I remember correctly), can I do similar with 
CentOS?

Thanks,

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org






More information about the CentOS mailing list