[CentOS] chown command goof up

Tue Feb 13 16:56:42 UTC 2007
Ross S. W. Walker <rwalker at medallion.com>

> -----Original Message-----
> From: centos-bounces at centos.org 
> [mailto:centos-bounces at centos.org] On Behalf Of David A. Woyciesjes
> Sent: Tuesday, February 13, 2007 8:36 AM
> To: CentOS mailing list
> Subject: Re: [CentOS] chown command goof up
> 
> Ross S. W. Walker wrote:
> >> -----Original Message-----
> >> From: David Woyciesjes [mailto:david.woyciesjes at yale.edu] 
> >>
> >>    So if I'm following this right, then I just need to run 
> >> rpm --setugids `rpm
> >> -qa` as root, from /, and this should set the owner & groups 
> >> on all files,  as
> >> appropriate? Except for of course the files in /home?
> >>     As for my original plan, I saw krename in yum. At first 
> >> glance, that looks
> >> like it should do what I wanted. Anyone have experience with it?
> > 
> > Not sure what krename does, but yes an rpm --setugids `rpm 
> -qa` and an
> > rpm --setperms `rpm -qa` will reset all file perms and 
> ownership for all
> > files managed under RPM.
> > 
> > I gave a simple awk command to reset the perms in /home in 
> an earlier
> > post, basically using awk to parse the passwd fields and 
> then issuing a
> > shell statement with them.
> 
> 	Thanks Ross. I didn't do anything with file permissions 
> (that I'm aware 
> of), so I shouldn't have to use the --setperms, right?
> 
> 	Just tried rpm --setugids `rpm -qa`, and got "sh: line 
> 2: package: 
> command not found". Now to figure out where that one comes from...

Make sure popt is installed, which version of CentOS is this?

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.