Skip to main content

RPM Command Cheat Sheet

RPM (Redhat Package Manager) is the most popular package utility and is used mostly on RHEL, Centos and Fedora.
RPM helps user/admins to build, install, query, verify, update, and remove/erase individual software packages.
More information can found rpm.org and techmint.com

Install Package

rpm -ivh [__rpmfile__]    
rpm -ivh vim-common-7.4.629-5.el6.i686.rpm
rpm -ivh --test vim-common-7.4.629-5.el6.i686.rpm

Upgrade Package

rpm -Uvh [__rpmfile__]    
rpm -Uvh vim-common-7.4.629-5.el6.i686.rpm
rpm -Uvh --test vim-common-7.4.629-5.el6.i686.rpm

Erase/Uninstall Package

rpm -ev [__package_name__]    
rpm -ev vim-common

Erase/Uninstall an installed package without checking for dependencies

rpm -ev --nodeps [__package_name__]    
rpm -ev --nodeps vim-common

List all installed packages

rpm -qa        
rpm -qa | grep vim 

Information along with package version and short description

rpm -qi [__package_name__]        
rpm -qi vim-common

Find out what package a file belongs to i.e. find what package owns the file

rpm -qf [__/path/to/file__]        rpm -qf /etc/passwd
rpm -qf /bin/bash

Display list of configuration file(s) for a package

rpm -qc [__pacakge_name__]
rpm -qc httpd

Display list of configuration files for a command

rpm -qcf [__/path/to/file__]        
rpm -qcf /usr/X11R6/bin/xeyes

Display list of all recently installed RPMs

rpm -qa --last        
rpm -qa --last
rpm -qa --last | less

Find out what dependencies a rpm file has

rpm -qpR [__rpmfile__]
rpm -qR [__package_name__]

rpm -qpR vim-common-7.4.629-5.el6.i686.rpm
rpm -qR bash

Comments

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa