Hi All,
I a working on configuring a not-quite minimal installation of CentOS 6.2. I tried doing the "minimal" installation available with the installer, but it's a bit too minimal to be useful. So I'm cutting down from a less minimal starting place. I'm pretty familiar with 5.x, but what I'm finding in 6.2 is a lot of new stuff, and a lot of odd behavior. For example, cups is starting at boot time, despite being disabled by chkconfig. And I'm finding things like qpidd, matahari, messagebus, and portreserve that really don't belong in a minimal setup.
To clarify, I'm shooting for a simple config, like one would use for a dedicated DNS server.
Can anyone point me to an up-to-date list of daemon processes that indicates what they do and whether they can be safely disabled? Also, any ideas as to what would be launching cups would be appreciated.
Thanks, --Bill
On Tue, 24 Apr 2012 16:22:17 -0700, listmail wrote
Also, any ideas as to what would be launching cups would be appreciated.
I answered one of my own questions: cups was being started by the VMware tools startup script. I fixed this for now by editing the VMware startup script and removing the command that starts it.
Still interested in a list of daemons that can be cleanly stopped, if one exists for 6.2 yet.
Thanks, --Bill
On 4/24/2012 7:22 PM, listmail wrote:
I a working on configuring a not-quite minimal installation of CentOS 6.2. I tried doing the "minimal" installation available with the installer, but it's a bit too minimal to be useful. So I'm cutting down from a less minimal starting place. I'm pretty familiar with 5.x, but what I'm finding in 6.2 is a lot of new stuff, and a lot of odd behavior. For example, cups is starting at boot time, despite being disabled by chkconfig. And I'm finding things like qpidd, matahari, messagebus, and portreserve that really don't belong in a minimal setup.
To clarify, I'm shooting for a simple config, like one would use for a dedicated DNS server.
Can anyone point me to an up-to-date list of daemon processes that indicates what they do and whether they can be safely disabled? Also, any ideas as to what would be launching cups would be appreciated.
I did a 'basic server' for my dns and then did this for cleaning up...
yum install yum-cron logwatch bind bind-chroot yum-cron
remove packages
yum remove samba-winbind-clients qpid-cpp-client matahari* cups
the two clients will get rid of a lot.
chkconfig atd off chkconfig autofs off chkconfig kdump off chkconfig netfs off chkconfig nfslock off chkconfig rpcidmapd off chkconfig rpcgssd off chkconfig rpcbind off
I left the rest on but that pretty much did it for me.. here is my chkconfig list, off and on
/root$ chkconfig --list |grep "3:on" abrt-ccpp 0:off 1:off 2:off 3:on 4:off 5:on 6:off abrt-oops 0:off 1:off 2:off 3:on 4:off 5:on 6:off abrtd 0:off 1:off 2:off 3:on 4:off 5:on 6:off acpid 0:off 1:off 2:on 3:on 4:on 5:on 6:off auditd 0:off 1:off 2:on 3:on 4:on 5:on 6:off cpuspeed 0:off 1:on 2:on 3:on 4:on 5:on 6:off crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off haldaemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off ip6tables 0:off 1:off 2:on 3:on 4:on 5:on 6:off iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off irqbalance 0:off 1:off 2:off 3:on 4:on 5:on 6:off lvm2-monitor 0:off 1:on 2:on 3:on 4:on 5:on 6:off mcelogd 0:off 1:off 2:off 3:on 4:off 5:on 6:off mdmonitor 0:off 1:off 2:on 3:on 4:on 5:on 6:off messagebus 0:off 1:off 2:on 3:on 4:on 5:on 6:off named 0:off 1:off 2:on 3:on 4:on 5:on 6:off network 0:off 1:off 2:on 3:on 4:on 5:on 6:off ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off portreserve 0:off 1:off 2:on 3:on 4:on 5:on 6:off postfix 0:off 1:off 2:on 3:on 4:on 5:on 6:off rsyslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off sysstat 0:off 1:on 2:on 3:on 4:on 5:on 6:off udev-post 0:off 1:on 2:on 3:on 4:on 5:on 6:off yum-cron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
/root$ chkconfig --list |grep "3:off" atd 0:off 1:off 2:off 3:off 4:off 5:off 6:off autofs 0:off 1:off 2:off 3:off 4:off 5:off 6:off certmonger 0:off 1:off 2:off 3:off 4:off 5:off 6:off cgconfig 0:off 1:off 2:off 3:off 4:off 5:off 6:off cgred 0:off 1:off 2:off 3:off 4:off 5:off 6:off kdump 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:off 4:off 5:off 6:off nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off nfslock 0:off 1:off 2:off 3:off 4:off 5:off 6:off ntpdate 0:off 1:off 2:off 3:off 4:off 5:off 6:off oddjobd 0:off 1:off 2:off 3:off 4:off 5:off 6:off psacct 0:off 1:off 2:off 3:off 4:off 5:off 6:off quota_nld 0:off 1:off 2:off 3:off 4:off 5:off 6:off rdisc 0:off 1:off 2:off 3:off 4:off 5:off 6:off restorecond 0:off 1:off 2:off 3:off 4:off 5:off 6:off rngd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcbind 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcgssd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcidmapd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcsvcgssd 0:off 1:off 2:off 3:off 4:off 5:off 6:off saslauthd 0:off 1:off 2:off 3:off 4:off 5:off 6:off smartd 0:off 1:off 2:off 3:off 4:off 5:off 6:off sssd 0:off 1:off 2:off 3:off 4:off 5:off 6:off ypbind 0:off 1:off 2:off 3:off 4:off 5:off 6:off
I recently did a minimal 6.2 install recently, and it was annoying that it didn't include the network stack.
What use is an install w/o the network? === Al
________________________________ From: Bob Hoffman bob@bobhoffman.com To: CentOS mailing list centos@centos.org Sent: Tuesday, April 24, 2012 5:18 PM Subject: Re: [CentOS] Not Quite Minimal CentOS 6.2
On 4/24/2012 7:22 PM, listmail wrote:
I a working on configuring a not-quite minimal installation of CentOS 6.2. I tried doing the "minimal" installation available with the installer, but it's a bit too minimal to be useful. So I'm cutting down from a less minimal starting place. I'm pretty familiar with 5.x, but what I'm finding in 6.2 is a lot of new stuff, and a lot of odd behavior. For example, cups is starting at boot time, despite being disabled by chkconfig. And I'm finding things like qpidd, matahari, messagebus, and portreserve that really don't belong in a minimal setup.
To clarify, I'm shooting for a simple config, like one would use for a dedicated DNS server.
Can anyone point me to an up-to-date list of daemon processes that indicates what they do and whether they can be safely disabled? Also, any ideas as to what would be launching cups would be appreciated.
I did a 'basic server' for my dns and then did this for cleaning up...
yum install yum-cron logwatch bind bind-chroot yum-cron
remove packages
yum remove samba-winbind-clients qpid-cpp-client matahari* cups
the two clients will get rid of a lot.
chkconfig atd off chkconfig autofs off chkconfig kdump off chkconfig netfs off chkconfig nfslock off chkconfig rpcidmapd off chkconfig rpcgssd off chkconfig rpcbind off
I left the rest on but that pretty much did it for me.. here is my chkconfig list, off and on
/root$ chkconfig --list |grep "3:on" abrt-ccpp 0:off 1:off 2:off 3:on 4:off 5:on 6:off abrt-oops 0:off 1:off 2:off 3:on 4:off 5:on 6:off abrtd 0:off 1:off 2:off 3:on 4:off 5:on 6:off acpid 0:off 1:off 2:on 3:on 4:on 5:on 6:off auditd 0:off 1:off 2:on 3:on 4:on 5:on 6:off cpuspeed 0:off 1:on 2:on 3:on 4:on 5:on 6:off crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off haldaemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off ip6tables 0:off 1:off 2:on 3:on 4:on 5:on 6:off iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off irqbalance 0:off 1:off 2:off 3:on 4:on 5:on 6:off lvm2-monitor 0:off 1:on 2:on 3:on 4:on 5:on 6:off mcelogd 0:off 1:off 2:off 3:on 4:off 5:on 6:off mdmonitor 0:off 1:off 2:on 3:on 4:on 5:on 6:off messagebus 0:off 1:off 2:on 3:on 4:on 5:on 6:off named 0:off 1:off 2:on 3:on 4:on 5:on 6:off network 0:off 1:off 2:on 3:on 4:on 5:on 6:off ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off portreserve 0:off 1:off 2:on 3:on 4:on 5:on 6:off postfix 0:off 1:off 2:on 3:on 4:on 5:on 6:off rsyslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off sysstat 0:off 1:on 2:on 3:on 4:on 5:on 6:off udev-post 0:off 1:on 2:on 3:on 4:on 5:on 6:off yum-cron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
/root$ chkconfig --list |grep "3:off" atd 0:off 1:off 2:off 3:off 4:off 5:off 6:off autofs 0:off 1:off 2:off 3:off 4:off 5:off 6:off certmonger 0:off 1:off 2:off 3:off 4:off 5:off 6:off cgconfig 0:off 1:off 2:off 3:off 4:off 5:off 6:off cgred 0:off 1:off 2:off 3:off 4:off 5:off 6:off kdump 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:off 4:off 5:off 6:off nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off nfslock 0:off 1:off 2:off 3:off 4:off 5:off 6:off ntpdate 0:off 1:off 2:off 3:off 4:off 5:off 6:off oddjobd 0:off 1:off 2:off 3:off 4:off 5:off 6:off psacct 0:off 1:off 2:off 3:off 4:off 5:off 6:off quota_nld 0:off 1:off 2:off 3:off 4:off 5:off 6:off rdisc 0:off 1:off 2:off 3:off 4:off 5:off 6:off restorecond 0:off 1:off 2:off 3:off 4:off 5:off 6:off rngd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcbind 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcgssd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcidmapd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rpcsvcgssd 0:off 1:off 2:off 3:off 4:off 5:off 6:off saslauthd 0:off 1:off 2:off 3:off 4:off 5:off 6:off smartd 0:off 1:off 2:off 3:off 4:off 5:off 6:off sssd 0:off 1:off 2:off 3:off 4:off 5:off 6:off ypbind 0:off 1:off 2:off 3:off 4:off 5:off 6:off _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 04/24/2012 08:53 PM, Al Sparks wrote:
I recently did a minimal 6.2 install recently, and it was annoying that it didn't include the network stack.
What use is an install w/o the network?
It has the network stack ... you must configure it during the install.
If you do not configure and enable the ethernet card then it does not turn on by default ... but it is in the installer to be able to do:
http://wiki.centos.org/FAQ/CentOS6#head-b67e85d98f0e9f1b599358105c551632c6ff...
You're right. The stack was there.
First, I was inaccurate when I said I installed 6.2. I actually installed 6.0, and later updated via yum.
Second, yeah I was able to start the network service, so there was a stack. All I'd get would be the loopback or "lo" interface, but it was there.
But going into /etc/sysconfig/network-scripts was a pain because there was no ifcfg-eth0 file I could play with. That's when I gave up and re-installed, but added more stuff beyond "base" just to be sure.
As for not configuring the network during the install process, I was pretty sure I had. For some reason it didn't take. Maybe I didn't click a save box when I should have. I don't know. === Al
________________________________ From: Johnny Hughes johnny@centos.org To: centos@centos.org Sent: Tuesday, April 24, 2012 6:04 PM Subject: Re: [CentOS] Not Quite Minimal CentOS 6.2
On 04/24/2012 08:53 PM, Al Sparks wrote:
I recently did a minimal 6.2 install recently, and it was annoying that it didn't include the network stack.
What use is an install w/o the network?
It has the network stack ... you must configure it during the install.
If you do not configure and enable the ethernet card then it does not turn on by default ... but it is in the installer to be able to do:
http://wiki.centos.org/FAQ/CentOS6#head-b67e85d98f0e9f1b599358105c551632c6ff...
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Tue, Apr 24, 2012 at 11:02:49PM -0700, Al Sparks wrote:
You're right. The stack was there.
First, I was inaccurate when I said I installed 6.2. I actually installed 6.0, and later updated via yum.
Second, yeah I was able to start the network service, so there was a stack. All I'd get would be the loopback or "lo" interface, but it was there.
But going into /etc/sysconfig/network-scripts was a pain because there was no ifcfg-eth0 file I could play with. That's when I gave up and re-installed, but added more stuff beyond "base" just to be sure.
As for not configuring the network during the install process, I was pretty sure I had. For some reason it didn't take. Maybe I didn't click a save box when I should have. I don't know.
My recollection (from installing 6.0 a couple times) is that even if you check the aforementioned checkbox during the install, once you're done, the network is not (properly) configured. I think there's a bug on that in the "upstream" bugzilla.
I do believe it has been fixed in 6.2, though.
(this is all from memory, I didn't look it up, so YMMV.)
On 04/25/2012 01:02 AM, Al Sparks wrote:
You're right. The stack was there.
First, I was inaccurate when I said I installed 6.2. I actually installed 6.0, and later updated via yum.
Second, yeah I was able to start the network service, so there was a stack. All I'd get would be the loopback or "lo" interface, but it was there.
But going into /etc/sysconfig/network-scripts was a pain because there was no ifcfg-eth0 file I could play with. That's when I gave up and re-installed, but added more stuff beyond "base" just to be sure.
As for not configuring the network during the install process, I was pretty sure I had. For some reason it didn't take. Maybe I didn't click a save box when I should have. I don't know. === Al
From: Johnny Hughes johnny@centos.org To: centos@centos.org Sent: Tuesday, April 24, 2012 6:04 PM Subject: Re: [CentOS] Not Quite Minimal CentOS 6.2
On 04/24/2012 08:53 PM, Al Sparks wrote:
I recently did a minimal 6.2 install recently, and it was annoying that it didn't include the network stack.
What use is an install w/o the network?
It has the network stack ... you must configure it during the install.
If you do not configure and enable the ethernet card then it does not turn on by default ... but it is in the installer to be able to do:
http://wiki.centos.org/FAQ/CentOS6#head-b67e85d98f0e9f1b599358105c551632c6ff...
Don't get the wrong idea here ... I think it is a very silly way to do installs to not default with the network turned on. It should be turned on ... but upstream decided it differently and I do not get to be the decider :D
One way to always get it to work is to do a network install. By default, you will get the same network after install that you input to do the install.