Hi Brian,
I checked out the latest trunk of oodt 0.5 and installed it.
After I set up the file manger and pushpull framework, I ran the
pushpull script.
As I described below, I think that the trunk is useful to fix the
problem, which was caused by handling ftp protocol.
INFO: Successfully
Hey YunHee,
You need to configure you mime-types.xml file in your policy directory to map
your file names to filemgr ProductTypes... if you want to just download the
files for now just comment out the filemgr
URL property in your pushpull properties file... if you want to configure the
Hi Chris,
When the environment variable FILEMGR was commented, pushpull
successfully downloaded a file from the remote side specified in
RemoteSpecs.xml. I checked the file was in the staging area as
follows:
yhkang@yunhee-kisti:~/oodt-0.5/cas-pushpull/staging/TESL2CO2$ ls
Hi YunHee,
I'll be sure to make sure OODT-474 is applied soon enough. Please see my patch
that I attached to the issue and let me know if it looks right.
Cheers,
Chris
On Jul 29, 2012, at 4:42 PM, YunHee Kang wrote:
Hi Chris,
Hi Chris,
Few days ago, Brian gave information about a new
Hi YunHee,
On Jul 29, 2012, at 4:32 PM, YunHee Kang wrote:
Hi Chris,
When the environment variable FILEMGR was commented, pushpull
successfully downloaded a file from the remote side specified in
RemoteSpecs.xml. I checked the file was in the staging area as
follows:
Hi YunHee,
Thanks! Can you file a JIRA issue about this and provide a patch?
Cheers,
Chris
On Jul 29, 2012, at 4:56 PM, YunHee Kang wrote:
HI Chris,
I forget that there was a problem when I ran the pushpull script.
$./pushpull
Word too long.
I thinks the problem is caused by csh
HI Chris,
I forget that there was a problem when I ran the pushpull script.
$./pushpull
Word too long.
I thinks the problem is caused by csh shell.
So To fix the problem, I modified the pushpull script based on bash.
The following statements are changed in the original pushpull script.
set
