Re: Serious performance bug in Perl
-> As the proud owner of that particular patch, I guess I should say
-> something... :)
->
-> >>>>> "Daniel" == Daniel Martin at cush <dtm12@jhunix.hcf.jhu.edu> writes:
-> Daniel> Ok, I've looked at it.
->
-> Daniel> I really don't know quite what to do with this. On the
-> Daniel> one hand, automatically reading the shadow password
-> Daniel> entries is desireable since it keeps old scripts working
-> Daniel> without knowing whether shadow passwords are being used or
-> Daniel> not. On the other hand, doing a getspnam for every getpw*
-> Daniel> call causes serious performance issues.
->
-> When I wrote the patch, I didn't have a 3000 entry /etc/passwd so was
-> unaware of any major performance issue with getspnam.
->
-> Daniel> The solution, as I said before, seems to be invoking some
-> Daniel> kind of magic on the scalar that's second in the list
-> Daniel> returned by getpw*. (what traditionally is the encrypted
-> Daniel> password field)
->
-> This, IMHO, is overkill. A less intrusive solution may be to do an
-> setspent call in the setpwent code within p_sys.c. Unfortunately, my
-> getspent man page seems to have gone missing so I can't check on the
-> feasiblity of this solution right now.
The best solution would be (imho) password database as some *NIXes use.
...and maybe some caching server for it ?
--
Matus "fantomas" Uhlar, sysadmin at NETLAB+ Kosice, Slovakia
BIC coord for *.sk; admin of netlab.irc.sk; co-admin of irc.felk.cvut.cz
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: