11 October 2015

How to fix keyring password problems in CentOS with Gnome desktop. (and maybe other distributions using Gnome as well?)

Snip ------
You can always wipe out your current keyrings by removing the file ~/.gnome2/login.keyring, but you should try resetting the password with the 'seahorse' program. Reinstalling gnome would do nothing, since it's all in your homedir.
 Unsnip ------

This was part of an exchange in the fedora forums, and was easily overlooked as it was part of a larger issue that was, thankfully,  solved.

Another part of this exchange was the following information regarding autologin, and how to disable it.

Snip -------
It sounds like you have auto-login enabled. Not sure how you managed that (is this a LiveCD?), but you can disable that by editing /etc/gdm/custom.conf and removing the lines between the [daemon] line and the [security] line.
Unsnip -------

I hope this helps someone else as much as it has helped me. :-)

The first fix regarding gnome keyring was the issue I experienced, and the second part regarding autologin was something that caught my eye as being useful in the future

Bye for now.

Have fun everyone!

08 October 2015

What to do when running "service named status" gives an rndc communication error?

 Do this and it should fix it.
I've had this issue with CentOS 5.x and 6.x at various times.
This will generate a new rndc key, and automatically configure rndc for you.

Thanks to the Serverfault.com and Linuxquestions.org websites for the answer.

rndc-confgen -a -r /dev/urandom
If you're using bind-chroot, add :
rndc-confgen -a -r /dev/urandom -t /var/named/chroot
The result should be:
wrote key file "/etc/rndc.key"
wrote key file "/var/named/chroot/etc/rndc.key"