Dan Peterson writes: > > But the interesting thing is, none of the current list of 15 procs older > than 24 hours logged one of these KEEPALIVE message. At least I assume I > should see the same process id in /var/adm/messages as the current "hung" > process?
No, CVS doesn't log its pid. What you think are pids in the syslog are probably uids. > What does "Invalid argument" in the context of setsockopt mean anyway? > The Solaris man page for setsockopt doesn't even show that EINVAL is a > valid error response. Well, an obvious guess is that it means that SO_KEEPALIVE isn't a valid socket option, but I think you really need to consult some Solaris experts to find out what's really going on. -Larry Jones Pitiful. Just pitiful. -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
