[Klug-general] Keeping Files in sync but local
David Halliday
david.halliday at gmail.com
Fri Feb 4 11:13:30 UTC 2011
1, 2, 3 : rsync can do this
4: I see your difficulty with rsync... However an SVN, CVS or GIT repository
will require by its nature a central structure of storage.
5: I'm not sure about this one personally.
I used to make configuration files available on a network shared drive.
Computers booted using their local configuration, part of the boot process
(early on) included a script to pull in updates over the network (when
available). If it is application configurations then this sort of solution
might be easier.
I think under windows that you can have a sort of cached network drive
storage... I'm sure that something similar must exist on *nix platforms.
On 3 February 2011 19:39, Peter Childs <pchilds at bcs.org> wrote:
> I'm looking for a method, to do the following?
>
> 1. Mainly for keeping config files in sync between multiple boxes but may
> also be other data files. ie the password files.
> 2. File must be local so it can be accessed even before the network is
> working or while part of the network is broken, or while a use is away from
> the network.
> 3. Files must be synced as soon as possible, or when we get back to the
> office.
> 4. There is no master so you can't just copy the master once its been
> updated. (so I can't just scp or rsync them in crontab)
> 5. Tell any programs reading the files that they have been updated, (Like
> Logrotate does)
>
> I'm sure there should be a simple way of doing this, but I'm not even sure
> of the right words to use on Google.....
>
> Thanks
>
> Peter.
>
> _______________________________________________
> Kent mailing list
> Kent at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/kent
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/kent/attachments/20110204/29d8fc05/attachment.htm>
More information about the Kent
mailing list