> Might it be better to set the permissions to allow everyone > to read/write? if the directory already exists because of > some other process, our stealing it might break something > else. also mkdir -p will not complain if the directory > already exists.
I see your point. Right now the fix restricts write access to the sipxchange user only and would have the potential of creating high CPU conditions for any Java-based process that is not running is sipxchange. This is in fact the case for our Java-based setup utilities but it's somewhat of a non-issue because of their short-lived nature. I'm on the fence on that one. On one hand, there are no non-transient Java processes in our system that do not run as sipxchange so there isn't a real need today to open the permissions wider than they need to be (how many negatives can one pack in a single sentence? :) ). On the other, if for some reason we add in the future a non-transient Java-based process that does not run as sipxchange then the high CPU utilization will come back... Not sure what the right trade-off is - anybody? > > > ________________________________ > > From: [email protected] > [mailto:[email protected]] On Behalf > Of [email protected] > Sent: Tuesday, March 16, 2010 9:35 AM > To: [email protected] > Subject: sipXecs 18322 rjoly: [XX-7634] - create the > temporary directory used by IBM's Attach API with proper > permissions to avoid high CPU utilisation problems > > > Project sipXecs > New Revision 18322 > <http://code.sipfoundry.org//changelog/sipXecs/?cs=18322> > Committer rjoly > Date 2010-03-16 08:34:30 -0500 (Tue, 16 Mar 2010) > > Log > > > [XX-7634] - create the temporary directory used by > IBM's Attach API with proper permissions to avoid high CPU > utilisation problems > > > > Modified: > > > * main/sipXpbx/etc/init.d/sipxecs.in > <http://code.sipfoundry.org//browse/sipXecs/main/sipXpbx/etc/i > nit.d/sipxecs.in?r1=18321&r2=18322> > > _______________________________________________ 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/
