I don't know, but if you haven't changed your CVS client then it looks like you have a security issue. I believe if you aren't using a lock server for CVS that's running on the server, then CVS has to perform writes into the repository's CVSROOT directory to temporarily lock files during an update. You may not have write access to CVSROOT, and this is why your update (which you expect to be reading files) is failing.
- CVS update fails with "Broken pipe" Klaus Zeitler
- Re: CVS update fails with "Broken pipe" Andy
- Re: CVS update fails with "Broken pipe" Todd Denniston
