Scott Lawrence wrote: > On Mon, 2009-05-04 at 09:59 -0400, Damian Krzeminski wrote: >> http://track.sipfoundry.org/browse/XX-5396 >> >> We now have a patches that trigger upgrades through XML/RPC >> But Bogdan reports that XML/RPC for upgrades does not work reliably. >> >> Can anyone help testing this? > > Have you got a binary setuid wrapper for the 'yum update -y' command? > That command can only be run as root, and sipXsupervisor is running as > SIPXPBXUSER.
Paraphrasing a sipXecs coordinator let me ask "what do you mean by you?" ;-) Unless I misunderstood something sipXconfig user does not really matter here: sipXconfig calls XML/RPC method and sipx-supervisor that implement the method needs to be able to run those scripts. > > The path issue that Bogdan describes will happen only in developer > builds; we need to do something about it (probably in the build > environment setup), but in the production builds the paths do not have > any '..' segments in them. > > I am not worried too much about the developer at this point. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
