[EMAIL PROTECTED] wrote:
> I use a home-brew backup script that basically loops through some
> directories, grabbing a wad of files, tar/gzip them up, and FTP the
> result to a distant server. To minimize space footprint, it deletes
> the file after FTP finishes, but it's a very primitive setup
On Feb 12, 2008 6:13 PM, <[EMAIL PROTECTED]> wrote:
> >Agreed :-) I just glanced over your email, but you do know about
> screen right?
>
> Wasn't that the thing that let you run multiple windows in a
> command-line terminal?
Correct. Screen is really awesome. I almost refuse to use any shell
th
>Default number of TCP retries is 6 in exponential backoff and should
>time out after a few minutes. That's how long you have to
>resynchronize your TCP stream before the other end destroys the
>session...
Ten panicked seconds shouldn't be a problem then.
>TCP ensures that data is not corrupted
On Feb 12, 2008 4:41 PM, <[EMAIL PROTECTED]> wrote:
> 1- If I left it for a while instead of a few panicked seconds, it
> would timeout and drop the connection, ending FTP and moving on to the
> next file. This would result in a lost file.
Default number of TCP retries is 6 in exponential backo
I use a home-brew backup script that basically loops through some
directories, grabbing a wad of files, tar/gzip them up, and FTP the
result to a distant server. To minimize space footprint, it deletes
the file after FTP finishes, but it's a very primitive setup-- no error
catching and retryin
