yum commands history

By -
[root@GFS13864 ~]# yum history
Loaded plugins: product-id, refresh-packagekit, rhnplugin, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
This system is receiving updates from RHN Classic or RHN Satellite.
ID     | Login user               | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
    12 | System            | 2015-01-07 15:18 | Update         |    1
    11 | root               | 2014-12-23 07:38 | I, U           |    7
    10 | root               | 2014-12-23 07:12 | Install        |    1
     9 | root               | 2014-12-19 09:49 | Install        |    1  <
     8 | root               | 2013-12-29 21:31 | Install        |    3 ><
     7 | root               | 2013-11-21 20:37 | Install        |    2 >
     6 | root               | 2013-11-21 20:36 | Install        |    1
     5 | root               | 2013-11-21 20:36 | Install        |    1  <
     4 | root               | 2013-11-10 01:16 | Install        |    2 >
     3 | root               | 2013-03-18 06:53 | Install        |    2
     2 | root               | 2013-03-18 06:44 | Install        |   73
     1 | System            | 2013-03-13 04:06 | Install        | 1371
history list
[root@GFS13864 ~]# yum history info 12
Loaded plugins: product-id, refresh-packagekit, rhnplugin, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
This system is receiving updates from RHN Classic or RHN Satellite.
Transaction ID : 12
Begin time     : Wed Jan  7 15:18:44 2015
Begin rpmdb    : 1494:39c23bbf4675a4d36e96d7227ca28c85ca403cdc
End time       :            15:18:55 2015 (11 seconds)
End rpmdb      : 1494:9689a36fc0adb64924ceea359b24a40aac85b9b7
User           : System
Return-Code    : Success
Transaction performed with:
    Installed     rpm-4.8.0-32.el6.x86_64                 @anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4
    Installed     yum-3.2.29-40.el6.noarch                @anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4
    Installed     yum-metadata-parser-1.1.2-16.el6.x86_64 @anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4
Packages Altered:
    Updated bash-4.1.2-14.el6.x86_64     @anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4
    Update       4.1.2-15.el6_4.2.x86_64 @rhel-x86_64-server-6.4.z
history info
[root@GFS13864 ~]#

Comments

Post a Comment

Popular posts from this blog

How to delete SEA in VIOS

By -
Remove the network en0 #ifconfig en0 down #ifconfig en0 detach Delete SEA $ lsdev -type sea name             status      description ent27            Defined     Shared Ethernet Adapter $ chdev -dev en26 -attr state=detach en27 changed $ rmdev -dev ent26;rmdev -dev en26;rmdev -dev et26 ent27 deleted $ rmdev -dev en26 en27 deleted $ rmdev -dev et26 et27 deleted system information #prtconf|more rmdev -dev ent3;rmdev -dev en3;rmdev -dev et3
Read more

Webmin configuration for LDAP

By -
We cannot add or delete users by default so we have to do below changes in LDAP module in GUI mode only. Configuring the module The most complex part of using this module is configuring it to talk to your LDAP server. By default, it will attempt to auto-detect the settings by looking at the LDAP client settings on your system, documented on the LDAPClient page. However, if this fails (perhaps because the LDAP server is not one of its own clients), you will need to configure the module manually as follows : On the module's main page, click on the Module Config link. In the LDAP server host field, enter the hostname of your LDAP server. If it is running on the same machine, enter localhost. If the LDAP server is using encryption, change the LDAP server uses TLS? option to Yes. In the Bind to LDAP server as field, enter the full DN of the administrative user for your LDAP server. This might be something like cn=Manager,dc=my-domain,dc=com. In the Credentials for bind name above field,...
Read more

Sample questions and answers for AWS Associate Solutions Architect Certification ---> AWS exam dumps

By -
Sample questions and answers for AWS Associate Solutions Architect Certification I try to give value for this by providing more information than the answer Q.What does Amazon S3 stand for? A.Simple Storage Service. Q:You must assign each server to at least _____ security group A:1  Q:Before I delete an EBS volume, what can I do if I want to recreate the volume later? A:Store a snapshot of the volume  http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-deleting-volume.html Q:Select the most correct answer: The device name /dev/sda1 (within Amazon EC2 ) is _____ A:Reserved for the root device  Q:If I want an instance to have a public IP address, which IP address should I use? A:Elastic IP Address http://aws.amazon.com/articles/1346 Q:What does RRS stand for when talking about S3? A:Reduced Redundancy Storage  http://aws.typepad.com/aws/2010/05/new-amazon-s3-reduced-redundancy-storage-rrs.html Q:All Amazon EC2 instances are assigned two IP addresses at lau...
Read more