Alan DeKok a �crit:
Degrande_Samuel <[EMAIL PROTECTED]> wrote:
I tried to track it and found the memory leak to be IN the solaris
pam modules. After some talks with other people, it seems that
every pam implementation (Solaris, Linux...) suffers from memory leak, and everybody tell to use a forked process to proceed the pam
authentication. What do you think of that ?
It's horrible.
I'm fully agree with you ! But it seems to be the way used by some other sofware which needs PAM authentication (like pop servers, for example). The problem is that PAM was rather created for only one authentication per thread, as someone told me.
I could propose you a rlm_pam module which fork a new child every <given_number> authentication request.
I would rather fork a seperate program via Exec-Program-Wait, which did the PAM authentication.
Well, if your seperate program is killed and restarted from time to time, that would be fine.
Regards.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
