Dan Foster wrote: > You could truss it. E.g.: > > $ truss -f -o /tmp/truss.log basename > > ...and see if something stands out. >
Nothing stands out, except the bind failure so_socket(2, 2, 0, "", 1) = 4 bind(4, 0xFFBEF558, 16, 3) Err#13 EACCES Then it closes down and writes out the error > Also, check a few things: > > $ ls -l /usr/bin/rcp /usr/bin/rsh /usr/bin/rlogin > > Are all three owned by root and is mode 4755? If not, set accordingly. > Yep, all look good. I just ran pkgchk against the whole machine, and nothing stands out from there either. -spp _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
