On Fri, Apr 10, 2009 at 6:15 AM, Daniel Drake d...@laptop.org wrote:
No, since after the XS tools delete it, it doesn't know if the data on
the remote server is new or not. (it doesn't keep other records other
than the synchronized file)
So how can the XS tools know that there is _new_ data to
2009/4/10 Martin Langhoff martin.langh...@gmail.com:
On Fri, Apr 10, 2009 at 6:15 AM, Daniel Drake d...@laptop.org wrote:
No, since after the XS tools delete it, it doesn't know if the data on
the remote server is new or not. (it doesn't keep other records other
than the synchronized file)
On Wed, Apr 8, 2009 at 12:30 AM, Daniel Drake d...@laptop.org wrote:
xs-activation-import unconditionally deletes the lease files from the
directory that it imports. This doesn't play nice with a system such
as puppet, which we're using here:
Ouch. The XS tools in general are expecting other
2009/4/9 Martin Langhoff martin.langh...@gmail.com:
The strategy I'm working towards is of atomic drop-box style
directories (write a tempfile, mv it to the dropbox). If puppet is in
charge of putting the file in its actual destination, then it's in
charge of triggering the read new file /
Hi,
xs-activation-import unconditionally deletes the lease files from the
directory that it imports. This doesn't play nice with a system such
as puppet, which we're using here:
we configure puppet to send a json file full of leases to the server,
and when that file is changed puppet then runs
