/usr/local/samba/sbin/winbindd broken?
Rowland Penny
repenny at f2s.com
Thu Aug 30 02:55:19 MDT 2012
On 30/08/12 08:54, Kai Blin wrote:
> On 2012-08-29 16:51, Rowland Penny wrote:
>
> Hi Rowland,
>
>> As some of you may know, I have been testing nmbd,smbd& winbindd from
>> Samba 4 as a client.
>> Well, after a good bit of testing and scratching of head, I have come to
>> the conclusion that something in the /usr/local/samba/sbin/winbindd
>> daemon is broken.
> Ok, just to be sure, on the S4 client, you're running smbd, nmbd and
> winbindd, but not the "samba" binary?
>
> Anything interesting in the winbind logs?
>
> Cheers,
> Ka
>
I am just running the three daemons:
ps ax | grep samba
2914 ? Ss 0:00 /usr/local/samba/sbin/nmbd -D
2916 ? Ss 0:00 /usr/local/samba/sbin/smbd -D
2917 ? S 0:00 /usr/local/samba/sbin/smbd -D
2919 ? Ss 0:00 /usr/local/samba/sbin/winbindd -D
2921 ? S 0:00 /usr/local/samba/sbin/winbindd -D
There is nothing in the logs apart from showing the daemons starting &
stopping. I have even looked in the logs on the server, nothing there
either.
Stop me if I am wrong, but as far as I am aware, winbind is supposed to
pull the posix info from the server database. If this is so, then
/usr/local/samba/sbin/winbindd is broken, as I only get the non-posix
info i.e. it does not work like S3 winbind.
Rowland
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the samba-technical
mailing list