On Mon, 2010-03-15 at 13:28 -0400, Robert Joly wrote: > To prove the theory, I added the following two lines to > the do_setup() function of the sipxecs launch script before launching > any process and the CPU problem goes away immediately: > mkdir /tmp/.com_ibm_tools_attach/ > chown sipxchange:sipxchange /tmp/.com_ibm_tools_attach/ > > Do these two lines seem like a decent approach to solving the high CPU > problem or does anybody have a more clever approach to ensuring that > /tmp/.com_ibm_tools_attach/ permissions allow our Java-based sipXecs > processes to write to it?
Rather than putting them into the launch script, it would be better to create a setup hook script with a very low sort order (they are launched in order by name). The script will be run as root, but could create those with whatever permissions are needed. I'd like to know what that's being used for, and whether or not there are security implications ... _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
