winbind "warm up" period?

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marc Kaplan wrote:
| Jerry,
|
| Just a note that I'm seeing this too. Once winbindd starts, it is about
| 15-20 seconds before it can answer any wbinfo queries. For example wbinfo
| -p, wbinfo --sequence, and wbinfo -m all fail with the same error code
as if
| winbindd were not running. I.e. "Could not YYY" where YYY is what you're
| trying to do. Shouldn't the wbinfo command just wait until winbindd is
able
| to answer these queries rather than acting like winbindd is not alive?


Did you troubleshoot any name resolution issues like I suggested?
Tail log.winbindd at level 10 and see where is gets stuck.



cheers, jerry
~ ----------------------------------------------------------------------
~ Hewlett-Packard            ------------------------- http://www.hp.com
~ SAMBA Team                 ---------------------- http://www.samba.org
~ GnuPG Key                  ---- http://www.plainjoe.org/gpg_public.asc
~ "You can never go home again, Oatman, but I guess you can shop there."
~                            --John Cusack - "Grosse Point Blank" (1997)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/e0Y1IR7qMdg1EfYRAlc3AJ9n9GnL0gADu1yUNw3OxXkm1WtYqQCcCNbL
DvorZ1gMVXsCezgKhNmw/wI=
=Zydb
-----END PGP SIGNATURE-----