Hello [EMAIL PROTECTED],
This might be completely unrelated, but I've noticed some other odd stuff.
When reading directories with links, or the links themselves, sometimes
strage things happen, example:
*reading a dir*
## list: read ftp://ftp.aminet.net/pub/aminet/recent/
URL Parse: none none ftp.aminet.net none pub/aminet/recent/ none
Net-log: [["PORT" port/locals/active-check] "200"]
Net-log: "200 PORT command successful."
--snip--
Net-log: [["LIST" "."] ["150" "125"]]
Net-log: {150 Opening BINARY mode data connection for /bin/ls.}
Net-log: [
none "226"]
** Access Error: Network timeout.
** Where: list: read ftp://ftp.aminet.net/pub/aminet/recent/
(to start with, modem lamps blink happily, but after a short while there's
no activity and then later comes the timeout)
*reading a file*
## file: read ftp://ftp.aminet.net/pub/aminet/recent/AMP.readme
URL Parse: none none ftp.aminet.net none pub/aminet/recent/ AMP.readme
Net-log: [["PORT" port/locals/active-check] "200"]
Net-log: "200 PORT command successful."
--snip--
Net-log: [["RETR" port/target] ["150" "125"]]
Net-log: {150 Opening BINARY mode data connection for AMP.readme (640 bytes).}
Net-log: ["low level read of " 22 "bytes"]
Net-log: [
none "226"]
Net-log: "226 Transfer complete."
== "Short: MPEG1/2,MP2/"
## print file
Short: MPEG1/2,MP2/
I'm not going through a firewall.
Best regards
Thomas Jensen
On 25-Feb-00, [EMAIL PROTECTED] wrote:
> I'm writing software to check for file changes at an ftp site, however...
>
> There are about 1500 files in one directory, each with a filename of 35
> characters - that's my problem I expect. With a normal -
>
> print read ftp://sitename/directory/
>
> You get as far as
>
> Net-log: {150 Opening BINARY mode data connection for /bin/ls.}
> Net-log: [
> none "226"]
>
> Then after several minutes
>
> ** Script Error: pick expected series argument of type: series money date
> time object port tuple any-function.
> ** Where: pick server-said 4
>
> The above read works fine on directories with only a few files.
>
> This is with REBOL 2.2.0.3.1.
> Is there a solution or workaround?
>
> Thanks - Nigel
>
>
