Alan Dayley writes: > > Over the course of a few days many cvs processes are piling up. > Eventually when about 40+ of them are open, the service stops responding > to clients. Then I manually kill the cvs processes and re-enable the > CVS service. Everything appear to work fine from the client side after > that. At least until too many processes are created.
Those would be server processes that are waiting for input from clients that have disappeared without cleanly disconnecting (which would have caused the server to shut down). So, it would appear that you are using defective clients (or misusing correct clients). CVS tries to use the SO_KEEPALIVE socket option to detect such disappearing clients, so it would appear that your system doesn't have that option, it doesn't work correctly, or it waits way too long before declaring the connection dead. -Larry Jones Aw Mom, you act like I'm not even wearing a bungee cord! -- Calvin
