search for: chain_proto

...he script). I couldn't understand why this was happening, until I noticed that it was looking in /etc/protocols and not finding what it was looking for. After reading the code in the current repository, I noticed that parse_protocol calls getprotobyname before it looks in the internal table, chain_protos. It was causing problems with '-p all' since 'all' is not likely to be in the /etc/protocols file causing NSS to fall through from files to ldap. Only after the ldap request had timed out did it use its own local table to process 'all.' I'm not sure if this has been...