Displaying 1 result from an estimated 1 matches for "source_hom".
Did you mean:
source_home
2013 Apr 10
1
Winbind using 100% CPU
...922e in s3_event_loop_once () from /lib64/libsmbconf.so.0
#7 0x000000381d204060 in _tevent_loop_once () from /lib64/libtevent.so.0
#8 0x000000000042049a in main ()
Apparently it's stuck in the winbindd_reinit_after_fork (and more
specifically the _talloc_free function). This code resides in
$SOURCE_HOME\source3\winbindd\winbindd_dual.c.
Perhaps I have configured Samba incorrectly? Here are the parameters I am
using that have to do with winbind:
idmap config * : backend = nss
idmap config * : range = 1000 - 300000
What are some reasons that winbind is using 100% CPU and how can I resolve
this?...