samba - Jun 2006 - I have no winbind pipe!

I configured samba to run as a file server in an NT domain by hand, and all
was going well except there were some permission problems. I decided to
install and use SWAT to configure samba, but now I cant even ping winbind. I
found that someone else had this problem and solved it by deleting the pipe
at /tmp/.winbindd/pipe , but when I ran an ls ?A command in /tmp I found
there was no ".winbindd". Any help would be greatly appreciated?
--
View this message in context:
http://www.nabble.com/I-have-no-winbind-pipe%21-t1794490.html#a4889989
Sent from the Samba - General forum at Nabble.com.

> I configured samba to run as a file server in an NT domain by hand,
> and all was going well except there were some permission problems. I
> decided to install and use SWAT to configure samba, but now I cant
> even ping winbind. I found that someone else had this problem and
> solved it by deleting the pipe at /tmp/.winbindd/pipe , but when I
> ran an ls ?A command in /tmp I found there was no ".winbindd".
Any
> help would be greatly appreciated? --
What happens if you run winbindd from the command line in debug mode -
what do the errors say?

Cheers,
Adam.

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 <steele@agora-net.com>
To: sneezewort <sneezewort@msn.com>, samba@lists.samba.org
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