Yep, the vmware ones run processes that seem to attach to the kernel, but offer the vmware services. kill them and it should work.
#ps aux|grep vmware root 27401 0.0 0.0 1288 216 ? S Sep27 0:00 /opt/vmware/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0 root 27419 0.0 0.0 1504 364 ? S Sep27 0:00 /opt/vmware/bin/vmnet-natd -d /var/run/vmnet-natd-8.pid -m /var/run/vmnet-natd-8.mac -c /etc/vmware/vmnet8/nat/nat.conf root 27722 0.0 0.0 1284 216 ? S Sep27 0:00 /opt/vmware/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet8.pid /dev/vmnet8 vmnet8 root 27733 0.0 0.0 1516 424 ? S Sep27 0:00 /opt/vmware/bin/vmnet-dhcpd -cf /etc/vmware/vmnet8/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet8/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8 On Tue, 2003-10-07 at 19:06, a_k_b wrote: > modules dont have a pid!? > > > sorry, use "kill -9 <pid>" for the modules. > > -- > [EMAIL PROTECTED] mailing list -- William Kenworthy <[EMAIL PROTECTED]> -- [EMAIL PROTECTED] mailing list
