I wonder if part of the problem is with the gids map updating on all of the back-end nodes at the same time, and the NIS service is getting hammered.
-Chris On Mon, 12/18/06 03:06p EST, Jeff Squyres wrote: > > - I put some printf's in the code to show that the gid lookup for the > hash map does seem to be the culprit; the getgrent function runs > *much* faster on the head node than my compute nodes (suggesting some > kind of not-related-to-munge configuration problem on my compute > nodes -- I'm investigating). _______________________________________________ munge-users mailing list [EMAIL PROTECTED] https://mail.gna.org/listinfo/munge-users
