[Samba] Re: Configuring idmap for a Samba 3.2.4 AD member server

[David Eisner]

On Mon, Nov 10, 2008 at 3:42 PM, David Eisner <deisner at gmail.com> wrote:
> None of it mentions using "idmap config".  I may be mistaken, but I
> don't see anything in the HOWTO about using  "idmap config":
>
>    http://www.google.com/search?hl=en&q=inurl:Samba-HOWTO-Collection+"idmap+config"
>
> Where should I look for definitive, up-to-date instructions for
> configuring this with Samba 3.2.4?


While I wait for an answer, an update on two discoveries:

1. High CPU for winbindd process

This appears to have happened because I had "winbind cache time = 0"
in smb.conf. I set this to zero at some point to debug a previous
problem.  What happens with the cache time set to zero is that when
winbindd's main() calls process_loop() in an infinite loop (which is
normal), process_loop() in turn calls rescan_trusted_domains() many
times per second.  Normally this would just return without doing
anything until the cache had expired, but with the cache time
parameter set to zero, it queries the server, pegging the CPU and
generating much network traffic.

I don't recall this setting causing a problem in the past.  Perhaps a
redesign of the process loop at some point is responsible.  I think
there should be a warning in the smb.conf man page cautioning against
setting the winbind cache time to zero.


2. When I do a getent passwd, I see this in the winbindd log file:

[2008/11/11 13:24:26,  0] winbindd/winbindd.c:(633)
  request_len_recv: Invalid request size received: 2088 (expected 2096)
[2008/11/11 13:24:26,  0] winbindd/winbindd.c:(633)
  request_len_recv: Invalid request size received: 2088 (expected 2096)
[2008/11/11 13:24:26,  0] winbindd/winbindd.c:(633)
  request_len_recv: Invalid request size received: 2088 (expected 2096)

Is this normal?

Thanks again.

-David

-- 
David Eisner     http://cradle.brokenglass.com