Enable grub menu:
edit the /etc/default/grub file and change the
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
to
GRUB_HIDDEN_TIMEOUT=10
GRUB_HIDDEN_TIMEOUT_QUIET=false
Save and call:
sudo update-grub
from a terminal, and reboot.
Enable grub menu:
edit the /etc/default/grub file and change the
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
to
GRUB_HIDDEN_TIMEOUT=10
GRUB_HIDDEN_TIMEOUT_QUIET=false
Save and call:
sudo update-grub
from a terminal, and reboot.
On Debian based systems like Ubuntu:
# dpkg --list | grep linux-image
Type the following command:
# uname -r
# uname -mrs
With rpm based OSes
# rpm -qa kernel
This will list the available kernels.
Type the following command:
# uname -r
# uname -mrs
If an instance gets stuck in an intermediate state (e.g., “deleting”), you can manually reset the state of an instance using the nova reset-state command. This will reset it to an error state, which you can then delete. For example:
$ nova reset-state c6bbbf26-b40a-47e7-8d5c-eb17bf65c485
$ nova delete c6bbbf26-b40a-47e7-8d5c-eb17bf65c485
You can also use the --active to force the instance back into an active state instead of an error state, for example:
$ nova reset-state –active c6bbbf26-b40a-47e7-8d5c-eb17bf65c485
![]() |
Note |
|---|---|
The version of the nova client that ships with Essex on most distributions does not support the reset-statecommand. You can download a more recent version of the nova client from PyPI. The package name ispython-novaclient, which can be installed using a Python package tool such as pip. |
The log files are located here :
/var/logs/nova
Logfiles are :
nova-api.log
nova-cert.log
nova-compute.log
nova-dhcpbridge.log
nova-manage.log
nova-network.log
nova-objectstore.log
nova-scheduler.log
nova-volume.log
nova-xvpvncproxy.log
The magic spell is :
$sudo apt-get update; sudo apt-get upgrade
kickstart postinstall, you can read how to do this on the internet.
wget http://foo/tools.tar.gz
tar xzvf *.tar.gz
cd directory-where-you-untarred
vmware-tools-install.pl -d
BINGO !
Giggidi Giggidi
While this is a Linux forum this came in REALLY handy so what the heck 🙂
Frustratingly hidden away, windows command for putting the machine into Hibernate and / or standby are hidden away in the api under the powrprof.dll library.
Shutdown %windir%\System32\shutdown.exe -s
Reboot %windir%\System32\shutdown.exe -r
Logoff %windir%\System32\shutdown.exe -l
Standby %windir%\System32\rundll32.exe powrprof.dll,SetSuspendState Standby
Hibernate %windir%\System32\shutdown.exe -h OR
%windir%\System32\rundll32.exe powrprof.dll,SetSuspendState Hibernate
Also if you Windows 7 wakes up and you don’t know why check:
powercfg lastwake
Hope this helps.
Debian based systems use the file /etc/hostname to read the hostname of the computer at boot time and set it up using the init script /etc/init.d/hostname.sh
One can edit the file /etc/hostname and change the hostname and then run:
/etc/init.d/hostname.sh start
Update /etc/hosts ip 127.0.0.1 respectively ( leave the localhost entry untouched)
Steps:
Ref: http://sysblogd.com/50/change-hostname-permanently-on-debian-or-ubuntu.htm
Installing SNMP daemon and tools:
As root
yum -y install net-snmp.i686
yum -y install net-snmp-utils
Once these are installed start the snmp daemon:
/etc/init.d/snmpd start
chkconfig snmpd on
This is just the basic install but testing it :
snmpwalk -v 1 -c public -O e 127.0.0.1
For production servers it is advisable to at least change the community name.
All configs are in
/etc/snmp/snmpd.conf
and traps are setup here:
/etc/snmp/snmptrapd.conf
No traps are set by default.
Enjoy !!