Try starting apache under truss or strace or whatever system call tracing utility is appropriate for your OS. Then try your telnet test again and see what it says.
Be sure to use the option to enable tracing of forked children as well. On Mon, Jun 17, 2002 at 06:56:17PM -0700, Erik Curiel wrote: > > > > that telnet should show you what messages apache is sending to the > > client, if any. Keeping an eye on top while you do that might also > > give you insight as to whether any new threads are being launched to > > handle the request > > Thanks for the idea. I had already tried telnet'ing on 443, but I hadn't > tailed any logs while doing it. As the first time I tried, telnet'ing > returned no messages at all from apache, and no logs showed any activity > at all while I was telnet'ing. Fucking mysterious. > > Any more ideas would be greatly appreciated. > > Thanks. > > Erik > > > _______________________________________________ > Bits mailing list > [EMAIL PROTECTED] > http://www.sugoi.org/mailman/listinfo/bits -- ___________________________________________________________________ P a u l [EMAIL PROTECTED] _______________________________________________ Bits mailing list [EMAIL PROTECTED] http://www.sugoi.org/mailman/listinfo/bits
