[Swift-devel] Re: swift-falkon problem

[Zhao Zhang]

yep, the swift option only cares about "chdir". I am not sure that I 
have the SVN permissions to commit. That will be great, if you commit 
this to the SVN. :-)

zhao

Ioan Raicu wrote:
> What does the last option "swift" really do?  Is that the chdir?  If 
> yes, then it should be a default behavior (rather than an option) as 
> long as the directory field is specified.  Do you have SVN permissions 
> to commit changes?  If yes, you should commit this.  If not, I'll 
> commit it, and you need to get the permissions to commit code to the 
> Falkon SVN (I'll work on this).
>
> Ioan
>
> Zhao Zhang wrote:
>> Hi,
>>
>> The attachment is the BGexec source code to use with both non-swift 
>> and swift. To use it, first compile it like "gcc -o BGexec BGexec.c", 
>> run invoke it, run "./BGexec 127.0.0.1 55000 55001 -debug swift" the 
>> last option is to indicate that we are running BGexec with swift, if 
>> not simply change it to no.
>>
>> zhao
>>
>> Michael Wilde wrote:
>>> Sorry - another mis-diagnosis and incorrect conclusion on my part.
>>>
>>> Zhao just told me that we have out of date falkon worker code on the 
>>> sicortex that is not chdir'ing to the cwd arg of the falkon request.
>>>
>>> That explains what Im seeing. Its being fixed now and checked in.
>>>
>>> -- 
>>>
>>> To answer your questions though:
>>>
>>> Im running swift on a linux box bblogin.mcs.anl.gov
>>>
>>> It mounts the sicortex under /sicortex-homes
>>>
>>> I run swift from /sicortex-homes/wilde/amiga/run
>>>
>>> My sites file says:
>>>
>>> <pool handle="sico">
>>>       <gridftp  url="local://localhost"/>
>>>       <execution provider="deef"
>>>
>>> url="http://140.221.37.30:50001/wsrf/services/GenericPortal/core/WS/GPFactoryService"/> 
>>>
>>>       <workdirectory>/home/wilde/swiftwork</workdirectory>
>>> </pool>
>>>
>>> and /home/wilde/swiftwork on bblogin is a symlink to 
>>> /sicortex-homes/wilde/swiftwork
>>>
>>> so that when swift writes files to the sicortex dir (eg when it 
>>> creates shared/*) its using the same pathname that the worker-side 
>>> will use when the job runs.  Ie, even though the mount-points differ 
>>> between the swift host and the worker host, symlinks make the 
>>> workdir appear under same name on both sides.
>>>
>>> If NFS adheres to its close-to-open-coherence semantics, this then 
>>> should I think work.
>>>
>>> My scp-provider question is probably still worth answering and 
>>> trying if this doesnt work.
>>>
>>> - Mike
>>>
>>>
>>>
>>>
>>> On 3/17/08 2:57 PM, Ben Clifford wrote:
>>>> what does your filesystem layout look like?
>>>>
>>>> Where are you running swift? And where are you putting your 
>>>> scicortex site directory? On an NFS that is also accessible from 
>>>> your submit machine? If so, what path?
>>>>
>>>
>