Kumar, Subramaniam writes:
>
> The server process in our case runs on the Unix server. I thought there is
> only one server process serving the WinCVS client requests(corrrect me if I
> am wrong). Hence the server process will always be up and running.
No, inetd starts a separate server process for each client. When the
client is finished, it should close the connection which causes the
server to cleanup and exit.
> Even if a client crashes( I don't think this is happening here) after the
> timeout period , shouldn't CVS server clean up. That is not happening
> either.
Yes, but it can take quite a while for the server to time out. If the
system is rebooted in the meantime, or if someone kills the server
process with prejudice (i.e., kill -9), the server won't have a chance
to clean up.
> Yesterday when we noticed the problem , we saw few months old directories
> sitiing /tmp on the Unix server.
Has your system not been rebooted in months? If so, good for you! If
not, your system administrator probably should arrange for the /tmp
directory to get cleaned out on reboot. If all else fails, you might
want to have a cron job run periodically to cleanup old cvs server
directories, but that's really treating the symptom instead of the
problem.
-Larry Jones
I just can't identify with that kind of work ethic. -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
