Hi simon,
we even prefer to avoid having coda over-writing data. We will write
protect each run automatically after hitting the "end run button".
Starting today I will devote 100 % of me to the proceeding for your
conference (!)
-- tancredi
________________________________________________________________________________
Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124
research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
On Thu, 7 Nov 2002, Simon Sirca wrote:
> TB wrote:
>
> > Also, the data was automatically transferred to spuds. We can not avoid
> > overwriting with scp because we want to keep updating files for the
> > online analysis. Hence, runs 2330-2345 were also lost on the spuds.
>
> There are several ways to avoids mishaps like this. Already during
> the OOPS runs, we had a relatively simple, yet bullet-proof way
> of transferring run files between machines immediately after
> data acquisition was stopped. It went something like the xfer.sh
> which I attach. Checking of whether a given run was copied was done
> through dummy .copied files for each run, but can be done smarter.
> (The manual management of the run list can be automated.)
> We had this running in the background for weeks on end without failure.
>
> Even more obvious to me would be the use of rsync which can be forced
> to use ssh and made to respect almost arbitrary update criteria on
> the remote host(s). The only problem could be the automatic
> authentication as it is possible with ssh.
>
> Simon
>
> --
> Simon Sirca
> Dept of Physics, University of Ljubljana Tel: +386 1 4766-574
> Jadranska 19 Fax: +386 1 2517-281
> 1000 Ljubljana, Slovenia
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:28 EST