>Subject: [sipX-dev] updating from sipXconfig
>
>http://track.sipfoundry.org/browse/XCF-2954
>
>Bogdan published his work-in-progress patch for switching 
>sipXconfig updates to use XML/RPC. He has some questions: I 
>thought that posting on the list might bring some useful comments:
>
>Here it is:
>
><quoting from Bogdan's update>
>
>- first of all, i had to modify the HttpServer.cpp in 
>sipXtackLib project and to bypass some filename uri enforcing. 
>As i saw in code, for security reasons, the request to 
>retrieve published files that have filenames containing ".." 
>will fail. But the problem is that the files published by 
>sipXsupervisor (containing the stdout and stderr of the 
>updates-relative command invoked) are published with path 
>relative to the BUILD directory, containing ".." .
>
>In order to test the functionality of the patch I bypassed the 
>enforcing in HttpServer.cpp, but i think that the files should 
>be published with their absolute path rather than relative path.
>
>For example instead of:
> "/home/user/work/BUILD/../INSTALL/somedir/../anotherdir/file.err"
>
>it should be published as
> "/home/user/work/INSTALL/anotherdir/file.err"
>
>- the patch worked for version and for check-update just fine. 
>However, for update command it just keeps running and it 
>doesn't seem to stop. I checked the system processes and saw 
>that one "sipx-swadmin.py" and one "yum update -y" processes 
>were still running even after few hours. Trying to update 
>manually, using the same "yum update -y" command, it finished 
>in just few minutes successfully updating sipx. I couldn't 
>figure why the update from application remain in running state 
>and doesn't stop.
>
></quoting from Bogdan's update>
>
Bogdan,
   Did you check the error or stdout files created by the python script?
I'm curious if there is something in there indicating an issue.  It's
been quite a while since I wrote it and at the time I was able to
successfully update using the XML/RPC API via the sipxproc tool.

Raymond
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to