Cami Sardinha ?????: > Artem Bokhan wrote: > >> Under high load policyd (1.81) stalls with 100% cpu load and excessive >> select() in strace.... >> Any suggestions? >> > > What types of load? What do you mean? :) policyd begin to eat 100% of one cpu core, even after stopping postfix. The only way to fix that is restarting policyd.
> Why are there so many concurrent connections open > to Policyd? Possible because of a lot of client connections.... > What is the maximum amount of connections you've configured > Policyd to allow? > > I don't see if that is configurable.... If you mean defaults in Makefile and policyd.h - I didn't change them. >How many concurrent postfix processes are allowed? What about >memory on the system -- are you swapping or not? 1.5k processes max, I have about 5k connections per minute in peaks. As a workaround I decreased the number of processes to 500. The system is not swapping. > Cami > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > policyd-users mailing list > policyd-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/policyd-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
