[gin-data] Update Ftp transfers

Aleksandr Konstantinov const at takas.lt
Tue Aug 29 19:10:44 CDT 2006


  My point is interoperability test is supposed to test interoperability of
some actions/operations/whatever. Making it in exotic way involves additional actions,
not intended initially. So instead of checking gridftp protocol interoperability
we are testing handling of special files and filesystems interoperability.
As result obtained results may mean not that they are supposed to mean
and hence their value is lost. 
Let's keep things simple. And for interoperability sake too.

A.K.



On Tue, 29 Aug 2006 18:06:52 -0500
"William E. Allcock" <allcock at mcs.anl.gov> wrote:

> Are you saying that the instructions to do a mem-to-mem transfer via
> /dev/zero to /dev/null don't work for some of the servers?  Is so, then
> clearly we need to update the instructions.  
> 
> Bill 
> 
> > -----Original Message-----
> > From: owner-gin-data at ggf.org [mailto:owner-gin-data at ggf.org] 
> > On Behalf Of Aleksandr Konstantinov
> > Sent: Tuesday, August 29, 2006 5:12 PM
> > To: Raj Kettimuthu
> > Cc: oxana.smirnova at hep.lu.se; gregor at mcs.anl.gov; 
> > gin-data at ggf.org; balazs.konya at hep.lu.se
> > Subject: Re: [gin-data] Update Ftp transfers
> > 
> > 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.
> > 
> > 
> 


-- 




More information about the gin-data mailing list