[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: none
Peter Peres <plp@actcom.co.il> writes:
>
> Re: server problem
>
> Ok. about races:
>
> The log_*() routines simply write to a file using a (hopefully) atomic
> single write. Even if there would be a race it would cause some sort of
> error in the calls. There are no errors in the calls and I check each and
> every return (excepting fprintf(), but I do check errors on logfp from time
> to time).
>
> Remeber that even if there was an error in the log writes and the child
> would run then the socket would be serviced. What happens is, there is
> simply no return (0) from fork.
>
> Remeber that the code works perfectly on a SUN machine and that httpd (NCSA)
> also displays the problem when run stand alone on the Linux machine.
>
This means that:
1. The child gets blocked. Check it with 'ps'
2. Or, there still is some kind of I/O error. Try to open another file
*after* returning from fork() in child, and write smth. to it...
--
-Alexander
==============================================================================
Alexander L. Belikoff abel@bfr.co.il
Berger Financial Research Ltd.
=============================================================================
Follow-Ups:
- Re: none
- From: Peter Lorand Peres <plp@actcom.co.il>
References: