Re: Any better now?

[Chris Faylor <cgf at cygnus dot com>]

On Thu, Aug 24, 2000 at 11:50:53PM +0200, Corinna Vinschen wrote:
>Chris Faylor wrote:
>> On Thu, Aug 24, 2000 at 03:30:57PM +0200, Corinna Vinschen wrote:
>> >Corinna Vinschen wrote:
>> >>
>> >> Chris Faylor wrote:
>> >> >
>> >> > I've checked in some patches to cygwin which fix inetd/telnet operation
>> >> > for me.  Do they work for you, Corinna?  I haven't tried sshd yet.
>> >
>> >BTW: You can't compare inetd/sshd operations since inetd uses
>> >service manager operations. The inetd child isn't a real child
>> >process but a thread which is forked by the service manager.
>> 
>> How about now.  I found a problem in syslog which would cause core dumps
>> depending on the state of the stack.  I also found a problem in select()
>> which would cause the "double character presses" required for ssh.
>
>in.telnetd still doesn't exit, still waisting 100% CPU. For some
>reason you can see it only in Task-Manager, not in `ps -el' output.

I only see this with the DLL that you build.  It seems to be consuming
the CPU after it has called ExitProcess.  Mine doesn't do this.

Are you killing in.telnetd.exe?  If so, I wonder what would happen if
you let it run.

>sshd parent still doesn't exit, still waisting 100% CPU. If you
>stop it by pressing Ctrl-C, it exits and every following client
>operation works. No "double character press" problem anymore.
>
>Isn't it interesting that the waiting parent (which shouldn't wait
>but should have exited) isn't in the Cygwin process list anymore?
>Cygwin seems to be sure that the process "has left the building"
>but it doesn't. Just a hint.
>
>Do you want my DLL again?

I guess.  Just send it to me personally, though, not to cygwin-developers.

cgf