[paja1]

Originally Posted by Yil

paja1: "This is usually caused by another thread holding the loader lock." HA! Since I don't believe it's possible to manipulate the loader lock directly and ioFTPD is not a dll with an initialize routine with strict restrictions on what can be done during initialization, I claim it shouldn't be ioFTPD's fault Not sure what it is doing that is triggering the bug, but I'll keep on trying to squash it and re-writing the way it listens for incoming control connections is one of two ideas to try... [update: this is the classic lockup bug in all it's annoying glory... sad to see it's not gone as this is confirmation].

Which 3rd party scripts are you using? The other idea I've recently thought of is that I need to protect TCL's socket and process creation much like I do in the server itself. I'm guessing IMDB lookups, or calls to zip,rar executables might make the problem more likely so if you are using them it might make sense. If you have a simple server then it's most likely not that...

Hi Yil, firstly thanks for your investigation.... but to the point.
Yes, I'm using http package.

package require http

proc get_url {url} {
  set h [http::geturl $url]
  set r [http::data $h]
  http::cleanup $h
  return $r
}

An http request is called after each login. But was called in version 6.* as well, without any problem at all.

The other thing i'm doing is calling "post-processing" executable like this:

iputs -nobuffer "Executing postprocessing..."
exec $cfg_postAction [string map {/ \\} $dir]
iputs -nobuffer "Done!"

... and yes, you are probably right, because ftp sometimes refuse to connect to http server.. or hangs after calling this external executable.

But i really don't think i;m doing something wrong... do i?

Do you won't more dumps from me? Or any additional files, info?

Thanks!