On Sat, Aug 28, 2004 at 06:23:38PM +0200, Michael Tautschnig wrote:- start the update-process from one single server, not on the clientUpdate has to be done on the client: how else can it access the local filesystem ? In my setup, the server starts the update processes on the clients via the backdoor-sshd.
scp was my solution...
- push the conffiles to the clientIn my setup, clients do a cvs update as the first step.- tell the client, what to do with the new files
For all of that I intend to use cvs-hooks and the rcsinfo-file; there I specify the command to run on the destination host;
I began implementing this, but canceled the automatic-push cvs hook really fast: as every human, an administrator may make mistakes. so before pushing conffiles to clients and killing 100 computer whith just one cvs commit, the new configuration has to be tested. Ideally you have a group of test clients, where you carefully observe the consequences of your changes. only if no problems occur there, you mark them as ready-for-production-use (we do this by "cvs tag"ing them STABLE).
Ok - so could you give a short explanation of how to use your packages or can that be found somewhere already? Some kind of step-by-step guide would be really nice...
Thanks in advance, Michael
