Re: Getting (Bad protocol 'tcp') errors under Solaris

Thank you. I ended up figuring it out using truss. The machine in question was 
recently added as an LDAP client and it was looking for the protocols stuff 
from the directory, which didn't have the data loaded.

On Monday 12 December 2005 16:16, Gisle Aas wrote:
> "Michael J. Freeman" <[email protected]> writes:
> > 500 Can't connect to rt.innocent.com:443 (Bad protocol 'tcp')
>
> This means that getprotobyname("tcp") fails.  On many Unix systems
> this is looked up from /etc/protcols.  Try:
>
>   $ perl -le 'print scalar(getprotobyname("tcp"))'
>
> This ought to print 6 on most systems.  If it doesn't try to run it
> under truss to figure out what is happening.
>
> --Gisle

-- 
Michael J. Freeman
NMS Development
Netco Government Services, Inc.
--
The world is full of willing people, some willing to work, the rest willing to 
let them.
	-- Robert Frost

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDnfeDUv/7ffX2I84RAkChAJ4i0v76HOtPFsmvjr5FOBgYredsKQCdF1xR
aF50SZwZlUnerNuG6b36EiA=
=gZ6A
-----END PGP SIGNATURE-----