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

Post a Comment

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

"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.
Post a Comment
Read more