What are my smbd's doing ? (was Re: [Samba] secrets.tdb locking

[Mac]

>On Mon, Jul 23, 2007 at 06:01:06PM +0100, Mac wrote:
>> >On one previous occasion, the whole thing seemed to grind to a virtual
>> >halt, and we suspected (but couldn't prove) that a locking battle over
>> >(something like) secrets.tdb was to blame.
>
>Can you just start winbind on that box? No libnss_winbind or
>winbind entries in /etc/nsswitch.conf necessary. Just start
>it, winbind then should proxy access to the DC's and give
>some relief on the mutex for the DC.

We already do.  (it's in the init.d script, so it's automatic as well)

# ps -ef | grep winbind
    root 24365 24364  1 09:11:55 ?        1:46 /usr/local/samba/sbin/winbindd -D
    root 24366 24364  1 09:11:56 ?        0:56 /usr/local/samba/sbin/winbindd -D
    root  2963 24364  0 09:58:14 ?        0:00 /usr/local/samba/sbin/winbindd -D
    root 24364     1  3 09:11:55 ?        6:38 /usr/local/samba/sbin/winbindd -D
    root  4233 28012  0 10:10:13 pts/2    0:00 grep winbind


I've just briefly upped the debug level to '3' (smbcontrol winbindd debug 3).
and there's nothing unusual looking there.

e.g.:-

[2007/07/24 10:15:25, 3, pid=24364] nsswitch/winbindd_sid.c:winbindd_gid_to_sid(477)
  [ 4346]: gid to sid 130
[2007/07/24 10:15:25, 3, pid=24364] nsswitch/winbindd_sid.c:winbindd_lookupname(103)
  [24366]: lookupname AD\Bacteriology
[2007/07/24 10:15:25, 3, pid=24364] nsswitch/winbindd_sid.c:winbindd_gid_to_sid(477)
  [ 4346]: gid to sid 130
[2007/07/24 10:15:25, 3, pid=24364] nsswitch/winbindd_sid.c:winbindd_lookupname(103)
  [24366]: lookupname AD\Bacteriology



I'm now confused. I thought 'smbd' did all its own lookups withthe DCs.
Should they in fact not be?  Should winbindd be doing it ?  

How do we tell 'smbd' to use 'winbindd' ?






                               Mac
          Assistant Systems Administrator @nibsc.ac.uk
                           mac at nibsc.ac.uk
   Work: +44 1707 641565          Everything else: +44 7956 237670 (anytime)