Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Jul 2002 17:01:59 -0500
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Gary Jennejohn <garyj@jennejohn.org>
Cc:        "Jack L. Stone" <jackstone@sage-one.net>, Thomas Connolly <tconnolly@electrosoftsolutions.com>, Freebsd-questions@FreeBSD.ORG
Subject:   Re: cron and cvsup
Message-ID:  <20020719220159.GA31880@dan.emsphone.com>
In-Reply-To: <200207192147.g6JLl1xQ062615@peedub.jennejohn.org>
References:  <3.0.5.32.20020719155914.025dd7b8@mail.sage-one.net> <200207192147.g6JLl1xQ062615@peedub.jennejohn.org>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 19), Gary Jennejohn said:
> "Jack L. Stone" writes:
> > Tom: For starters, here is a script with the cron below the script:
> > 
> > cvsupscript
> > #!/bin/sh
> > /usr/local/bin/cvsup -g -L 2 /usr/src/sage-supfile
> 
> I suggest adding -1 to the command line, otherwise cvsup will try
> forever to connect on failure, resulting in massive numbers of cvsup's
> running. I'm speaking from experience here, since I made that
> mistake when I first added cvsup as a cron job.

I also add "-l /tmp/cvs.LCK", to prevent multiple cvsups from running
at the same time.

-- 
	Dan Nelson
	dnelson@allantgroup.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020719220159.GA31880>