I have a few processes that simply will not die on my openbsd machine and i can't figure out how to get rid of it (without rebooting).
kill -9 PID will not kill the process(es), what other options do i have?
what i was doing:
i had apache running and apache would list files on a windows machine on my internal network. I was using sharity-light to mount a smb share onto my openbsd machine. i tried to use this combination to allow access to some ISO files for example. it worked just fine on a dir without many entries, but when i tried to enter a dir with alot of files, the process froze. i've rebooted all of the windows machines, but cannot unmount the shared drives in openbsd. i also cannot kill two instances of httpd. ps shows three instances of me trying to unmount the share, and even one rm -rf sitting there in limbo. any reference to the mounted dir in general locks up my terminal (even a root terminal). by reference i mean if i start typing in the path of the share, then hit tab to complete the name, it will hang.
it seems that my machine is pretty f*cked up and that maybe i should give in and reboot, but i hate to do the windows admin solution.
i need a n0cmonkey batsignal thing to show distress. help help there is a p133 in dire need of an ass kicking.
kill -9 PID will not kill the process(es), what other options do i have?
what i was doing:
i had apache running and apache would list files on a windows machine on my internal network. I was using sharity-light to mount a smb share onto my openbsd machine. i tried to use this combination to allow access to some ISO files for example. it worked just fine on a dir without many entries, but when i tried to enter a dir with alot of files, the process froze. i've rebooted all of the windows machines, but cannot unmount the shared drives in openbsd. i also cannot kill two instances of httpd. ps shows three instances of me trying to unmount the share, and even one rm -rf sitting there in limbo. any reference to the mounted dir in general locks up my terminal (even a root terminal). by reference i mean if i start typing in the path of the share, then hit tab to complete the name, it will hang.
it seems that my machine is pretty f*cked up and that maybe i should give in and reboot, but i hate to do the windows admin solution.
i need a n0cmonkey batsignal thing to show distress. help help there is a p133 in dire need of an ass kicking.
