Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!sdd.hp.com!cs.utexas.edu!sun-barr!newstop!texsun!csccat!camdev!mmuegel From: mmuegel@camdev.comm.mot.com (Michael Muegel) Newsgroups: comp.sys.apollo Subject: Re: reducing the delay between edrgy and getpwuid() etc ... Message-ID: <384@camdev.comm.mot.com?> Date: 19 Feb 91 18:59:46 GMT References: <1093@usage.csd.unsw.oz.au> Organization: Cellular Infrastructure Group, Motorola, Inc., Fort Worth, Texas Lines: 25 In article <1093@usage.csd.unsw.oz.au> cameron@spectrum.cs.unsw.oz.au writes: >My problem is currently that after I've called the make-an-account call, and >edrgy's replied with a prompt indicating all is happiness, I often won't be >able to successfully do a getpwuid() or getpwnam() on said account for quite >a while (typically about a minute). Currently I sit in a loop polling >getpwuid() and sleeping for 10 seconds until it works, so that the program >can continue on its way and make home directories and set ownership, etc. In my Perl scripts I wrote for our admins I simply parse edrgy -v -a login output. I know better than to even try to trust the /etc/passwd file ;-). We have a fairly large network (~130) and it seems to take an unberably long time for the passwd file to reflect the true state of the registry. Thats my two and a half cents worth, -Mike -- +-----------------------------------------------------------------------------+ | Mike Muegel | Internet: mmuegel@mot.com | | Software Tools Group | UUCP: uunet!motcid!muegel | | Fort Worth Research & Development Center | Voice: (817) 232-6129 | | Cellular Infrastructure Group | Fax: (817) 232-6081 | | Radio Telephone and Systems Group | Mail: 5555 North Beach St. | | Motorola, Inc. | Fort Worth, TX 76137 | +-----------------------------------------------------------------------------+