Patrick Powell wrote: > and then calls 'initgroups(user,pw->pw_gid)'
If you are using NIS and have a large 'group' map, then initgroups will be slow. NIS indexes the group map by group, not name. Therefore, in order to find out what groups a particular user is in, initgroups has to go through the entire group map. My experience is that it does it one group at a time (eg. one RPC transaction per group). This is so awesomely brain-dead that it defies imagination. My solution was to distribute /etc/group to each workstation and not use the NIS group map. The entire file gets into file cache and initgroups becomes instantaneous. Perhaps this is not your problem, but I thought I would mention it. -Rick -- |Rick Cochran phone: 607-255-7618| |Cornell CIT - Systems & Operations - Net-Print FAX: 607-255-8521| |730 Rhodes Hall, Ithaca, N.Y. 14853 email: [EMAIL PROTECTED]| ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
