You could run a chkconfig --del winbindd an then reboot. That way it won't start and you won't have to "kill".
Cheers, Travis ----- Original Message ----- From: Ryan Steele <[EMAIL PROTECTED]> To: sneezewort <[EMAIL PROTECTED]>, [email protected] Sent: Friday, June 16, 2006 1:40:19 PM GMT-0700 Subject: Re: [Samba] I have no winbind pipe! sneezewort wrote: > You can ping with "wbinfo -p" command. > I can't stop winbind, in fact I cant even "kill" it by pid. I even tried to > reboot, but winbindd is still unkillable, and no wbinfo or "net join" > commands work. I tried to do a full uninstall and reinstall, but the problem > remains. > -- > View this message in context: > http://www.nabble.com/I-have-no-winbind-pipe%21-t1794490.html#a4906659 > Sent from the Samba - General forum at Nabble.com. > > I have had Samba processes that do not respond to kill either. However, you can pass the kill command options that will sometimes help. kill -9 is the most severe, and in most cases will kill just about anything. (If it doesn't, you've got more serious issues with your kernel). However, make sure that there aren't more graceful ways first. Do a man kill to see what options there are. But, if all else fails, there is the -9. I know I've had to use it more than I'd like... Best, Ryan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
