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 pi
> 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 deleti
This is a copy and paste of commands I tried.
-
CPU:/# winbindd -d
CPU:/# winbindd -S -d
Can't log to stdout (-S) unless daemon is in foreground +(-F) or interactive
(-i)
Usage: [-?iV] [--usage] [-S ARG] [-F ARG] [-Y ARG]
> CPU:/# winbindd -i -S -d
> winbindd version 3.0.14a-Debian started.
> Copyright The Samba Team 2000-2004
> ERROR: winbindd is already running. File /var/run/samba/winbindd.pid
> exists and process id 8706 is running.
So winbindd is already running - you'll need to kill it and rerun it in
debug m
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 co
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
ay, 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,
OK I was able to get things back to the way it was by using Ryan Steele's
suggestion of kill -9, and deleting the SWAT smb.conf and starting from
scratch again. The problem is I’m back to where I was with the permissions
problem. I'll guess Ill start a new thread for that problem. Thanks for all
y
