Date: Wed, 11 Jun 2003 00:11:30 +1000 (EST) From: jason andrade <jason@rtfmconsult.com> To: Daniel Lang <dl@leo.org> Cc: Ken Smith <kensmith@cse.Buffalo.EDU> Subject: Re: [FreeBSD-Announce] FreeBSD 5.1 Released! Message-ID: <Pine.GSO.4.50.0306110009160.619-100000@luna.rtfmconsult.com> In-Reply-To: <20030610140733.GA65541@atrbg11.informatik.tu-muenchen.de> References: <20030610133105.GA66707@fit.vutbr.cz> <200306101348.h5ADmkeR091829@lurza.secnetix.de> <20030610140733.GA65541@atrbg11.informatik.tu-muenchen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Jun 2003, Daniel Lang wrote: > I participate in several push mechanisms. The best current practice > I know of uses ssh (v2) keys, which can be used to trigger just the > update skript. Data can be piped through the ssh call, but is not needed, > since the ssh call could trigger the fetching of a webpage with the data. what daniel said. the change control process on the master does its stuff and when all is synced, the person making the change can 'signal' all the tier-1 servers to start pulling data, via a 'push trigger'. if multiple ssh keys are generated, it is even possible to trigger different syncs for different parts of the archive - i speculate. regards, -jason
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.50.0306110009160.619-100000>