[Arthur de Jong]
> This can't be made configurable easily because this is about memory
> allocated in the NSS module. The NSS module doesn't parse the config
> file and doesn't hold any state (apart from the connection to nslcd for
> multi-call requests like {set,get,end}pwent()). The path to the socket,
> timing settings and buffer sizes are all compiled-in.

Well, the NSS part talk to the nslcd daemon, which do read the config
file and keep state, so the NSS module could fetch the configuration
over the socket. :)

Still, I would prefer it if there was no hard coded upper limit on the
number of group members handled.  Or at least a syslog message
explaining what is going on when the limit is reached.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to