# sysv-rc-conf 'servicename' off
I'd try first disabling all those vbox services, any audio services & saned and see how things run then.
In terms of SBS liking or not liking the hardware, I think it's more likely that some other process is occasionally fiddling with problematic hardware and somehow blocking SBS. As far as I know, the only system resources SBS consumes are networking, cpu and disk.
For my own servers, these are the simple rules I follow:
- Disable all unneeded hardware in BIOS (CPU virtualization support, 2ndary NIC, serial ports, audio hardware, etc.)
- Run the server headless, with no gui. (Not running a gui saves you loads of CPU cycles.)
- Only run services that are mission critical (e.g. samba, sbs, minidlna, lighttpd, rsync for me plus a few hardware monitoring services.)
- Only connect cables/peripherals that are used all the time (e.g. ethernet, usb data connection to the UPS, usb connected CM19a X10 transceiver.)
- Keep file systems simple. (I.e. keep audio/video and other data on a separate disk, ideally with an ext4 filesystem. For the OS disk, I don't even use LVM. Why add another layer of abstraction to a file system that will remain largely static?)
Again, I'm offering these in the spirit of 'this works for me'. I'm not claiming that these constitute some sort of deity-sanctioned best practice.
Results 11 to 11 of 11
2012-07-20, 13:20 #11