That worked well. I removed the "-q" from grep, so I could see what files were modified... and most were configuration files that I could disregard.
Thanks, Chris On 10/19/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote: > > On Oct 19 2007 09:11, Chris Worley wrote: > > > >I had to fsck recently, and lost+found had ~100 files when complete. > > > >I'd like rpm to go through the disk and identify missing or corrupt > >files, so I can reload the RPMs (maybe automatically). > > > >Is there any way to do that? > > rpm -V packagename | grep -P "^missing|^..5" > > but note that configuration files (which are valid to have been > modified (5)) will also show up. > > Pack up that rpm -V into a rpm -qa loop and perhaps collecting > the output, sort of > > list=""; > for i in `rpm -qa`; do > rpm -V "$i" | grep -Pq "^missing|^..5" && list="$list $i"; > done; > smart reinstall $list > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
