Greets all. I'm getting confused here.
>> mess: ["line one" "line two" {line thre"e} "line four"]
== ["line one" "line two" {line thre"e} "line four"]
>> write/lines ftp://user:[EMAIL PROTECTED]/dir/subdir/file.txt mess
connecting to: site.com
<working working>
** User Error: Failed login to site.com as user. Check your login
** Near: write/lines ftp://user:[EMAIL PROTECTED]/dir/subdir/file.txt mess
>>
Horse hockey! My usual FTP program lets me in OK. I've made sure of the
path and everything. The username and password are fine. In fact, I do
trace/net on and see this:
>> write/lines ftp://user:[EMAIL PROTECTED]/dir/subdir/file.txt mess
URL Parse: user pwd site.com none dir/subdir/ file.txt
Net-log: ["Opening tcp for" FTP]
connecting to: site.com
Net-log: [
none ["220" "230"]]
** User Error: Failed login to site.com as user. Check your login
** Near: write/lines ftp://user:[EMAIL PROTECTED]/dir/subdir/file.txt mess
>>
I've changed what the file should be, what the text is, not using /lines...
Ah, but the wonderful thing is when I do:
>> trace on
>> trace/net on
>> trace/function off
>> write/lines ftp://user:[EMAIL PROTECTED]/dir/subdir/file.txt mess
<removing all of the gory details>
Trace: if (word)
Trace: none? (word)
Trace: server-said: (set-word)
Trace: pick (word)
Trace: port (word)
Trace: 1 (integer)
** Access Error: Network timeout
** Where: confirm
** Near: write/lines ftp://user:[EMAIL PROTECTED]/dir/subdir/file.txt mess
>>
Does that make sense? Why does it suddenly change? I fiddled with the path
once, and it returned an error message saying the path was invalid and didn't
exist. So it's connecting, at least some times. In fact, it's even creating a
0 byte file (and over-writing any previous file in its place).. Help??
--Charles
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
