Originally Posted by deepugopi
Through ssh..i'll explain cvs-network in detail..We are currently working on different projects..So we had created different cvs repository for each project(total 3 cvs repositories)..
3 repositories are ..
Altogether 30 users are here out of which 5 are windows users & rest linux(RHEL Desktop or Mandriva)..Windows users are using wincvs 1.2 & linux users are using lincvs 1.4.3.Windows users connect to cvs-server through "ssh tunneling".Linux users connect to cvs-server through the port 2401.
At present when a user commits a change in the ic-repository(/ic/a), the other users who belong to that particular repository who get notification mail automatically...
If you'd have working solution then congratulation, and please share with us, otherwise I have 1 suggestions.
Already we are having the group-id for the ic-team..
Unfortunately I don't have any immediately solution, but I have is a work around solution (Which can be tricky)
My suggestion is,
Configure a start up script , when any ssh login will trigger the script and run some necessary action you want. (either ~/.bashrc, /etc/environment,/etc/profile,/etc/profile.d/automail or etc kind of way you prefer). The action can be check what current username, check what current cvs version (which is going to update), and etc.
If you want to maintain the server, create a specific username, inside the startup script purposely detect this kind of login won't trigger the email.
I hope you can understand and it is a long story to explain the scenario and logic. Simply plan for you strategy. However, before you ask us the next question tell us your strategy so we can suggestion what is the next step.