> Unfortunately I've run into the other problem, inetd reporting > a loop problem when I installed 2.4.2p2 (upgrade from 2.4.1p1) > on a Solaris 2.6 client of the same server. Changing the inetd > -r parameter did not resolve that issue for me so if anyone would > has any ideas...
Could you please post your inetd.conf lines and the syslog lines?
