Mark writes: > > Also, we got about 18 of the following in the /var/adm/messages > as well today, again starting with the 1.12.5 upgrade.... no > time pattern to these entries..... > > messages:Dec 30 09:29:14 batman cvs[12093]: [ID 666953 > daemon.notice] bad auth protocol start: EOF > messages:Dec 30 09:32:42 batman cvs[13517]: [ID 666953 > daemon.notice] bad auth protocol start: EOF
Typically, that indicates that someone is connecting to the pserver port and then closing the connection rather than starting the CVS client/ server protocol. Perhaps you're being port scanned. > What would really help is having the cvs username (I use a > non-root pserver) and the client machine/IP in the messages log > for these errors. Hopefully a user and/or machine pattern will > show up. There is no cvs username yet, that would have been sent in the authorization information that pserver was trying to read when it got end-of-file instead. CVS doesn't know anything about client machine names or IP addresses, that's all handled by [x]inetd. Perhaps you can arrange for [x]inetd to log the connections and then correlate the time stamps. > Any ideas on how these /var/adm/messages came into play on the > pserver upgrade? Newer releases of CVS tend to do more error checking and reporting than older releases. -Larry Jones Even if lives DID hang in the balance, it would depend on whose they were. -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
