Re: Netlink Socket Problem

What happens in real life is that passwd is going to log some data to the audit system and opens a socket, then it collects the passwords, if everything is OK, it passes the passwords to pam for authentication token update. Pam decides that it needs to do some logging of its own and opens descriptors to the audit system. They fail like above, EAGAIN. Does any of you kernel hackers know why apps are limited to 1 netlink socket connection? Can someone else verify the problem? I think I can fix the problem by constantly closing and opening connections, but that is ugly and not efficient. This "bug/feature" is holding up the release of the next version of audit and patched trusted programs.