(Solved) Curious about PCLinux services

[OrdiDoc]

The question is about Services in PCLinux OS. I'm so use to disable some of them in Windows that i'm curious about which one are really needed and in the list below is there any that i can stop on bootup that are not really necessary. I did a search on the forum but didn't find really what i was looking for.

acpid
alsa
apmd
atd
atieventsd
avahi-daemon
cpufreq
crond
cups
dm
haldaemon
ip6tables
iptables
irqbalance
kheader
laptop-mode
messagebus
mysqld
network
network-up
resolvconf
shorewall
sound
syslog
udev-post
uuidd
vboxadd-timesync
wine
xfs
xinetd

Remember, i don't want to create problems, just see if i can bootup with the minimum Services needed.

[Joble]

cpufreq network-up and wine can be turned off safely if you don't need them.  Not sure about the rest.

[OrdiDoc]

Thanks Jobie

[Neal ManBear]

If you're not using a printer, cups can be turned off.

[Bald Brick]

And if you're not running KDE on a laptop you won't need laptop-mode. At least I don't.

You won't need shorewall if you use another firewall. And I think you won't need vbox-timesync if you don't run VirtualBox (but I'm not sure).

To a certain extent it's a question of which services you need. You could probably even run your system without crond, but it seems to me that a Linux or UNIX system without cron wouldn't be a Linux or UNIX system ...

[jaydot]

one sure-fire way to find out if you need something is to switch one off, reboot and see how badly your system performs, if at all.  you will run the risk of possibly needing to reinstall, but it might be fun on a spare machine, or partition.  i ain't doin' it cos i'm set up beaut.

[Joble]

one sure-fire way to find out if you need something is to switch one off, reboot and see how badly your system performs, if at all.  you will run the risk of possibly needing to reinstall, but it might be fun on a spare machine, or partition.  i ain't doin' it cos i'm set up beaut.

I've broken my system many times, for many reasons, but that is a new level cruel jaydot.  I like it!   

[sixthwheel]

one sure-fire way to find out if you need something is to switch one off, reboot and see how badly your system performs, if at all.  you will run the risk of possibly needing to reinstall, but it might be fun on a spare machine, or partition.  i ain't doin' it cos i'm set up beaut.

I've broken my system many times, for many reasons, but that is a new level cruel jaydot.  I like it!   

I've done it. It's not like a car where you could crash into a tree or anything, if you start pulling stuff out of the engine.

[NoIBnds]

Tex posted a list sometime ago-- Here it is:

Core Services needed.
acpi
acpid
alsa
avahi-daemon
dm 
haldaemon
keytable   
messagebus
network     
network-up 
resolvconf   
sound         
uuidd         
xfs         

These go together if you want system logging enabled. If you never look in /var/log folder then you can turn these off.
atd
crond
syslog

These go together if you have a printer.
cups
portreserve

These go together if you need additional software security and not behind a router firewall.
ip6tables
iptables
mandi
msec 
shorewall 

These are needed turned on when you are installing a new kernel otherwise not needed at boot up.
dkms
kheader

These go together if you plan to share files over a network with other computers.
netfs *
portmap * 
smb *
snmpd
snmptrapd

This is needed if you plan to write to ntfs drive.
fuse

This is needed if you plan to run Virtualbox as it loads kernel drivers on start up.
virtualbox

This may be needed if you have a scanner.
xinetd

This turns on numlock. Great for desktops but can cause problems with some laptops
numlock

[Joble]

network-up is not mandatory.  It's the first thing I turn off and the biggest delay in my boot sequence.  It's a timer, to delay the boot until the network is up, what if you don't have a network?  I always turn it off, and it works.  Other than that NoIBnds:  Thanks!  I totally forgot about that.  Good Info.

[NoIBnds]

network-up is not mandatory.  It's the first thing I turn off and the biggest delay in my boot sequence.  It's a timer, to delay the boot until the network is up, what if you don't have a network?  I always turn it off, and it works.  Other than that NoIBnds:  Thanks!  I totally forgot about that.  Good Info.

I saved it so I would remember-- I just copied what Tex wrote and put it in a note to self. Glad it came in handy.

[OrdiDoc]

I have a second hard drive which contains a clone of the one that i'm using now so maybe i can use it and start removing some services and see how bad it performs but thanks for all the replies, great information