Can you provide a backtrace ? (FD_SET() might indeed segfault if you are setting a fd which is (far) above FD_SETSIZE)
-- Jille [email protected] schreef: > Thanx for reply, > I changed 2 files containing fd_setsize in /usr/include and recompiled php > and apache but didn't solve problem. > I found segfaults for vhosts's child process which has fopen() problem > > Segfaults appear both (1024,8192 I set) fd_setsize values > ------Original Message------ > From: Lazy > Sender: [email protected] > To: Peruser MPM List > ReplyTo: Peruser MPM List > Subject: Re: [peruser] PHP file open problem > Sent: Dec 7, 2009 9:50 PM > > 2009/12/7 Tolga <[email protected]>: > >> Hello everyone, >> >> >> >> I’m using peruser mpm in one of our web server (~950 vhosts). Our problem is >> some vhost has problems with file operations ( php foopen() file() ). >> >> Whenever occurred this situation apache didn’t write anything to access_log >> and anything appeared on browser >> >> I modify some limits.conf stuff but it didn’t solve anything. (I doublecheck >> limit status from /proc/_PID_/limits ) >> >> > > > you have to modify FD_SETSIZE in /usr/includes and recompile apache/php > _______________________________________________ > Peruser mailing list > [email protected] > http://www.telana.com/mailman/listinfo/peruser > > > Bu e-posta, Turkcell BlackBerry ile gönderilmiştir. > _______________________________________________ > Peruser mailing list > [email protected] > http://www.telana.com/mailman/listinfo/peruser > _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
