So say you happen to have 2 NICs of the exact same chipset, they will generally show up as the same name, with possibly a different revision in lspci. Normally this is not an issue if you have a server with 4 NICs, generally the eth0 to eth3 appears from left to the right (or right to left on some vendors) so it doesn't take much figuring out. Generally if you have different chipsets for different NICs, it should be easy to know which one is eth0 or the first NIC in the OS.........

Normally lspci will show you just like this and would suggest they are exactly the same card: 1a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] (rev e7) 1c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] (rev e7) lspci -vnn is the answer As we can see one is a Gigabyte and the other is an MSI card. Wha........

PHP Fatal error: PHP Startup: apc_shm_create: shmget(0, 67108864, 914) failed: Invalid argument. It is possible that the chosen SHM segment size is higher than the operation system allows. Linux has usually a default limit of 32MB per segment. in Unknown on line 0 PHP Fatal error: PHP Startup: apc_shm_attach: shmat failed: in Unknown on line 0 This error is not at all fun because it actually prevents Apache/httpd from starting or working at all. It will........

It is a permissions issue that is hard to fix. All but one USB device is greyed out. I am already a member of "vboxusers" I have already enabled and disabled USB support for the guest. I have already reinstalled the latest VBOx guest editions If running as root it all works fine Changing........

service monit status monit dead but subsys locked ........

If you move your hard drive(s) around to other computers/servers, you'll find that your eth0 keeps getting higher, the first time it will become eth1 and then eth2 etc and even higher if your server has dual or quad NICs. The reason is that udevd basically assigns eth0 tot he first NIC it finds and remembers it, if it encounters a NIC with a differentMAC, it assigns it one higher (eg. eth1). See the example below, I have eth2 now so how doI fix it?........

Inever started these processes but they are from a custom based bootable Linux I've made and I've never seen this behavior on other machines or even with the same machine using different kernels. These processes seemed to spawn on their own and I have no idea why and even worse why the CPU usage is so high? Here's the output from top: 907 extaudit 30 10 0 0 0 R 90.7 0.0........

kernel 2.6.27.54 Fusion MPT base driver 3.04.07 Copyright (c) 1999-2008 LSI Corporation Fusion MPT SPI Host driver 3.04.07 mptbase: ioc0: Initiating bringup mptbase: ioc0: WARNING - Unexpected doorbell active! mptbase: ioc0: ERROR - Doorbell ACK timeout (count=4999), IntStatus=80000001! mptbase: ioc0: ERROR - Diagnostic reset FAILED! (102h) mptbase: ioc0: WARNING - NOT READY! mptbase: ioc0: ERROR - didn't initialize proper........