As of today i'm using it on production environment. Let's hope nothing breaks. :-\
[EMAIL PROTECTED] wrote: > Hello, > > Quoting Stefan Seufert <[EMAIL PROTECTED]>: > >> I didn't have a chance to give it a try, but the patch itself looks >> fine. Maybe the remaining tasks are the multiplexers? They are never killed. >> >> I confirm that these are not multiplexers. They get born then theres something to do and go away then there isn't. And they are owned by specific user who's vhost is being accessed. >> Maybe someone should put together a mod_status like handler which >> outputs the contents of the scoreboard/child_info_table. >> >> > > mod_status is very welcome on my side since enabling debug mode eats up lots of resources and it very cpu intensive to get out real life info about what's going on. I get couple of GB of logs a day then debug is on and it's really a headache to build stats graphs out of it. But sorry, i'm just newbie then it comes to apache programming. I might fix something later , but not create it in the first place. > There is a debug mode in peruser mpm. You can just uncomment it (at start of > file) and see error_log in debug mode. > > I'm more than sure Stefan new that. _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
