[gin-data] Update Ftp transfers

[Aleksandr Konstantinov]

On Tue, 29 Aug 2006 15:27:38 -0500 (CDT)
Raj Kettimuthu <kettimut at mcs.anl.gov> wrote:

> On Tue, 29 Aug 2006, Aleksandr Konstantinov wrote:
> 
> > On Mon, 28 Aug 2006 17:07:35 -0500 (CDT)
> > Raj Kettimuthu <kettimut at mcs.anl.gov> wrote:
> >
> > > On Tue, 29 Aug 2006, Aleksandr Konstantinov wrote:
> > >
> > > > On Mon, 28 Aug 2006 16:05:45 -0500 (CDT)
> > > > Raj Kettimuthu <kettimut at mcs.anl.gov> wrote:
> > > >
> > > > > success :)
> > > >
> > > > Success (exit code 0) in most cases means failure for lseek() function, it
> > > > is supoosed to return location in file.
> > > >
> > >
> > > Right, but this does not really matter as we do /dev/zero to /dev/null
> > > transfers to imitate memory-memory transfers and to make sure there is no
> > > problem up till that point.
> >
> > What happens if multi-stream transfer is taking place and destination server
> > does lseek() on destination file /dev/null in order to store chunk of data at
> > proper position?
> 
> lseek() failure is ignored. lseek() would fail with pipes and non-files,

What makes You think lseek() failures are ifnored by ALL gridftp servers on market?
Anyway I wouldn't call application ignoring lseek() failures a properly behaving one.
IMO of course.

A.K.