Skip to main content

chkconfig is dead, long live chkconfig

I decided to watch my Fedora 16 box boot and I noticed that some iSCSI processes were failing.  Well, I don't need iSCSI anyhow - so, I may as well disable it.  Easy enough.

After I disabled the iSCSI bit, I wanted to see what other stuff was running and of course I was surprised when I found there were only 8 or so processes for runlevel 5.  I've discovered something I need to become more familiar with (systemd and systemctl).  For now... here's what I found.


[root@neo ~]# who -r 
         run-level 5  2011-12-30 16:24
[root@neo ~]# chkconfig --list | grep 5:on


Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by native
      systemd configuration.


autofs         0:off 1:off 2:off 3:on 4:on 5:on 6:off

iscsi           0:off 1:off 2:off 3:off 4:off 5:on 6:off
iscsid          0:off 1:off 2:off 3:off 4:off 5:on 6:off

netfs           0:off 1:off 2:off 3:on 4:on 5:on 6:off
sandbox         0:off 1:off 2:off 3:off 4:off 5:on 6:off
vmware         0:off 1:off 2:on 3:on 4:off 5:on 6:off
vmware-USBArbitrator 0:off 1:off 2:on 3:on 4:off 5:on 6:off
vmware-workstation-server 0:off 1:off 2:on 3:on 4:off 5:on 6:off
[root@neo ~]# chkconfig iscsi off
[root@neo ~]# chkconfig iscsid off 
[root@neo ~]# chkconfig --list 


Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by native
      systemd configuration.


autofs         0:off 1:off 2:off 3:on 4:on 5:on 6:off
ceph           0:off 1:off 2:off 3:off 4:off 5:off 6:off
dc_client       0:off 1:off 2:off 3:off 4:off 5:off 6:off
dc_server       0:off 1:off 2:off 3:off 4:off 5:off 6:off
ebtables       0:off 1:off 2:off 3:off 4:off 5:off 6:off
gfs2           0:off 1:off 2:off 3:off 4:off 5:off 6:off
ipsec           0:off 1:off 2:off 3:off 4:off 5:off 6:off
iscsi           0:off 1:off 2:off 3:off 4:off 5:off 6:off
iscsid         0:off 1:off 2:off 3:off 4:off 5:off 6:off
libvirt-guests 0:off 1:off 2:off 3:off 4:off 5:off 6:off
netconsole     0:off 1:off 2:off 3:off 4:off 5:off 6:off
netfs           0:off 1:off 2:off 3:on 4:on 5:on 6:off
network         0:off 1:off 2:off 3:off 4:off 5:off 6:off
sandbox         0:off 1:off 2:off 3:off 4:off 5:on 6:off
svnserve       0:off 1:off 2:off 3:off 4:off 5:off 6:off
vmware         0:off 1:off 2:on 3:on 4:off 5:on 6:off
vmware-USBArbitrator 0:off 1:off 2:on 3:on 4:off 5:on 6:off
vmware-workstation-server 0:off 1:off 2:on 3:on 4:off 5:on 6:off
zfs-fuse       0:off 1:off 2:off 3:off 4:off 5:off 6:off


[root@neo ~]#  systemctl -a | grep running

Comments

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un...