SUSEUnbound
Would you like to react to this message? Create an account in a few clicks or log in to continue.


 
HomeHome  PortalPortal  Latest imagesLatest images  SearchSearch  RegisterRegister  Log in  
openFate
Determining What's Been Changed on RPM Based Systems Fatelogo_small openFATE - openSUSE feature tracking
Similar topics
Latest topics
» Difference between 42.2 and 42.1
Determining What's Been Changed on RPM Based Systems Emptyby findoctr Thu Dec 15, 2016 7:53 pm

» openSUSE Leap 42.1 ?
Determining What's Been Changed on RPM Based Systems Emptyby findoctr Fri Feb 05, 2016 8:09 pm

» Happy Turkey Day
Determining What's Been Changed on RPM Based Systems Emptyby findoctr Thu Nov 26, 2015 1:45 pm

» Happy 4th of July!
Determining What's Been Changed on RPM Based Systems Emptyby bozo Sat Jul 04, 2015 12:56 pm

» It's been a while ...
Determining What's Been Changed on RPM Based Systems Emptyby bozo Mon Feb 23, 2015 8:34 pm

» Mondo chillers
Determining What's Been Changed on RPM Based Systems Emptyby bozo Wed Feb 18, 2015 5:11 am

Navigation
 Portal
 Index
 Memberlist
 Profile
 FAQ
 Search
IRC Channel
You can also find us on IRC's freenode.net as #suseunbound.

 

 Determining What's Been Changed on RPM Based Systems

Go down 
AuthorMessage
welan
Admin
welan


Posts : 248
Join date : 2010-02-23
Age : 61
Location : snow drift in minnesota

Determining What's Been Changed on RPM Based Systems Empty
PostSubject: Determining What's Been Changed on RPM Based Systems   Determining What's Been Changed on RPM Based Systems EmptyMon Mar 15, 2010 5:50 pm

As a "OS" consultant, I find myself working with several distros and other OS's. Some times though you find a tip or trick that is just so cool and useful......

I always find it useful to understand which files that shipped with rpm packages have been modified, since it's usually a good indicator of what customizations have been performed on the system. To determine the modified files, I simply run:

% rpm -qa | xargs rpm --verify --nomtime | less

# Sample output:

missing /usr/local/src
.M...... /bin/ping6
.M...... /usr/bin/chage
.M...... /usr/bin/gpasswd
....L... c /etc/pam.d/system-auth
.M...... /usr/bin/chfn
.M...... /usr/bin/chsh
S.5..... c /etc/rc.d/rc.local
S.5..... c /etc/sysctl.conf
S.5..... c /etc/ssh/sshd_config
S.5..... c /etc/updatedb.conf
The following is taken from the rpm man pages (Verify Options section):

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
Using this trick, I can quickly determine what configuration files have been modified as well as any metadata modifications (ownership, link etc.).
Back to top Go down
 
Determining What's Been Changed on RPM Based Systems
Back to top 
Page 1 of 1
 Similar topics
-
» Whats your input?

Permissions in this forum:You cannot reply to topics in this forum
SUSEUnbound :: Help Section :: Tips and Tweaks-
Jump to: