[Yil]

ZR: "Transfer_Buffer and (the obsolete?) Internal_Transfer_Buffer?". Internal_Transfer_Buffer is indeed obsolete, and from the ioFTPD.ini file you get this:

# This is the default size (it grows if needed) for internal buffering.
# It probably should be a multiple and at least as large as the data
# socket send size. Since internal buffers are used for directory listings
# it should be larger than the space needed for the largest single directory
# listing to avoid growing it. 32k min.
Transfer_Buffer = 131072

DataSocket_Send_Buffer = 32864

You probably won't need to change it.


HTTP service Messages. I looked at this and don't see where the heck it's resolving the path. I assume it's letting windows do the resolving so not sure why it isn't working... I'll look deeper if more people need this. The full path is a good workaround as that will definitely work.



tuff:

Haven't changed anything in iTCL so not sure why 5.8.8 would work and not 6.0. I tried this:

proc ytest {} {
iputs -nobuffer "testing 1 2 3"
}

ytest

outputs: testing 1 2 3

Am I missing something? It didn't look like it got encoded into unicode. Does it only happen with data you read from a file? Or do you have to read from a file and then iputs -nobuffer starts breaking? Wait, did you say 5.8.8 is working? I didn't think iTCL was working at all for 5.8.8. You sure it wasn't 5.8.5? I know I didn't make any changes, but it's totally possible someone changed something from 5.8.5 to 5.8.8...