Re: CVS - Automated builds

[Lamar Seifuddin]

Nils9

The problems I encountered were related to gmakefiles,etc.
None, so far with CVS.

But, I wanted to find out from your experience, what else may
be of some issues for me.

Thanks for sharing.

Lamar

Nils9 wrote:

> Tell us whats the problem you encountered.
> We ran into inetd protection, its something like- if more than 250 requests 
> per
> minute from same IP address to the same service then inetd stops the
> service for 10 minutes. And there is no way (in RadHat62) to configure it.
> Thats basically was the biggest pain, it was slow to make builds because
> we had to use delays in the script, and even then it kept failing.
> Also, there was mess with branches, but looks like this is somewhat clear
> to me finally ;-) (except the vendor branch, still have no idea why its 
> "special").
>
> -Nils Jakobsons
> SWH Technology
>
> ----- Original Message -----
> From: "Lamar Seifuddin" <address@hidden>
> To: "Nils9" <address@hidden>
> Cc: <address@hidden>
> Sent: Thursday, June 21, 2001 7:48 PM
> Subject: CVS - Automated builds
>
> > Hello,
> >
> > I have created an automated build script that checks out files from CVS,
> > also.
> > (CVS runs on Solaris)
> >
> > It works fine when I build from one src tree, but when I build from
> > multiple
> > src trees (cronjob), I run into problems.    I am not sure if it's
> > CVS-related or broken
> > code.
> >
> > What type of problems have you encountered?
> >
> > thanks,
> >
> >
> > Lamar
> >
> >
> >
> > Nils9 writes:
> > >
> > > I have people running automated build scripts which fetch files from
> > CVS
> > > (CVS runs on RedHat), and now it happens that the inettd locks down
> > > the service for 10 minutes - flood protection. We tried to insert
> > waitstates
> > > between CVS requests, it helped, but it gets soo long to build that
> > way.
> > > What are your reccomendations on this topic? How to disable this inetd
> >
> > > feature?  Could not find anything in manpages.
> >
> > Go read the inetd man page again, carefully.  I've never seen an inetd
> > that didn't have *some* way of adjusting the rate limit documented on
> > the man page.  Sometimes it's a command line option to inetd, other
> > times it's part of the entry in the config file.  And check that you're
> > really running inetd -- some systems use xinetd instead, in which case
> > you need to read its man page instead.
> >
> > -Larry Jones
> >
> > I hate being good. -- Calvin
> >
> >
> >
> >