[rhn-users] problems experienced with up2date

[Alfred Hovdestad]

Hi Rich.

I would check /etc/rc.d/rc.sysinit first.  First try changing the 
selinux content (C).  My rc.sysinit has:
# ls -lZ rc.sysinit
-rwxr-xr-x  root     root     system_u:object_r:initrc_exec_t  rc.sysinit

You should be able to set these with:

chcon -u system_u -t initrc_exec_t rc.sysinit

Then try the rpm -V initscripts again.  That should remove the C.  Then 
try the up2date again.  It should rename the new scripts as .rpmnew.  If 
the up2date does not succedd, you may have to look at what changes were 
made to the rc.local and rc.sysinit scripts.  You could try renaming 
them and copying a clean copy from another server, or simply rename them 
and try up2date without them.

Try that and let's see what happens.

    Alfred





Rich Archuleta wrote:
> Alfred,
> 
> The output is this:
> 
> rpm -V initscripts
> ..5....T. c /etc/inittab
> S.5....T. c /etc/rc.d/rc.local
> S.5....TC c /etc/rc.d/rc.sysinit
> 
> Regards,
> 
> - Rich Archuleta -
> 
> -----Original Message-----
> From: rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com]
> On Behalf Of Alfred Hovdestad
> Sent: Tuesday, July 10, 2007 10:22 AM
> To: Discussions about Red Hat Network (rhn.redhat.com)
> Subject: Re: [rhn-users] problems experienced with up2date
> 
> What is the output from rpm -V initscripts?   That should tell you what 
> has changed.  If a config file has changed, you can replace the config 
> file with the saved version (you did save the original, right?) or copy 
> the config file from a server running the same version of RHEL.
> 
> You can also edit the changed file (once you have identified it) to 
> remove the changes.  Once that is done, you should be able to run 
> up2date again.
> 
>    Alfred
> 
> 
>