rngd service fail

by default, centos 7 enables rngd.service, but it is configured for trust module or just plain misconfigured.



We can easily rectify the problem by editing the service  unit file: /usr/lib/systemd/system/rngd.service. The ExecStart line should be edited so that it reads as in the following:

ExecStart=/sbin/rngd -f -r /dev/urandom

This is also shown in the following screenshot:


We will need to reload the unit file once it has been edited. We can use the following command to achieve this:

# systemctl daemon-reload

With the new unit loaded we can now start the service and check the status:

# systemctl start rngd
# systemctl status rngd

The following video will step you through the process.


lvm.conf – initramfs

centos uses:

dracut -f

After updating /etc/lvm.conf, it’s necessary to update the initrd so that this file will be copied there, where the filter matters the most, during boot. Perform:

update-initramfs -u -k all

Every time either /etc/lvm.conf or /etc/multipath.conf is updated, the initrd should be rebuilt to reflect these changes. This is imperative when blacklists and filters are necessary to maintain a stable storage configuration.



Name        : gnome-shell-browser-plugin
Arch        : x86_64
Version     : 3.14.4
Release     : 53.el7
Size        : 39 k
Repo        : sl/x86_64
Summary     : Browser plugin to install extensions from extensions.gnome.org
URL         : http://live.gnome.org/GnomeShell
License     : GPLv2+
Description : The “GNOME Shell Integration” plugin provides integration with
: Gnome Shell for live extension enabling and disabling. It can
: be used only by extensions.gnome.org.

Launch google-chrome as another local user

setup group for sudoers system:

groupadd chrome

groupmems -a user -g chrome

launcher shell script

#! /usr/bin/sh
# sxh


sudo su – $USER -c “google-chrome $URL –display=$DISPLAY”

setup sudoers system:

  • group “chrome”
  • execute “/usr/local/bin/remote-chrome”
  • no password



#12007-10-07 18:40:47

From: City of Kol
Registered: 2006-07-01
Posts: 184

I’m running avahi 0.6.20. When I try to ping other comps on my LAN using ping hostname.local, it shows ping: unknown host. My machine can be pinged to by a Mac, but I can’t ping anyone using avahi. I read  on the Ubuntu wiki that this should work out of the box. Any reason why it doesn’t on Arch? I can see the machines through avahi-resolve-host-name and avahi-resolve-address.

EDIT: solved, thanks to http://gentoo-wiki.com/HOWTO_Zeroconf by modifying /etc/nsswitch.conf:

 hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4


hosts: files dns

Some people may experience a slight slowdown in DNS lookups due to this (at least in Ubuntu, I didn’t perceive much difference) according to this bug:

https://bugs.launchpad.net/ubuntu/+sour … +bug/94940

Last edited by abhidg (2007-10-07 19:01:12)