[rhn-users] problems experienced with up2date

[Alfred Hovdestad]

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



Rich Archuleta wrote:
> Thank you, Alfred.  How do I "fix" the situation so that I can move on
> and run "up2date -u"?
> 
> 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: Monday, July 09, 2007 4:39 PM
> To: Discussions about Red Hat Network (rhn.redhat.com)
> Subject: Re: [rhn-users] problems experienced with up2date
> 
> It is telling you that something has changed in your initscripts 
> package.  You can determine the changes with
> 
> rpm -V initscripts
> 
> 
> See man rpm for the meaning of the attributes:
> 
> 
>         c %config configuration file.
>         d %doc documentation file.
>         g %ghost file (i.e. the file contents are not included in the 
> package payload).
>         l %license license file.
>         r %readme readme file.
> 
> 
>         S file Size differs
>         M Mode differs (includes permissions and file type)
>         5 MD5 sum differs
>         D Device major/minor number mismatch
>         L readLink(2) path mismatch
>         U User ownership differs
>         G Group ownership differs
>         T mTime differs
>         C selinux Context differs
> 
> 
> Alfred
>