Scott Lawrence wrote: > On Wed, 2009-07-29 at 15:08 -0400, Arjun Nair wrote: >> Hi, >> >> Currently, to determine the SW version running on a system, we do a >> rpm query for the sipXcommons rpm, and then parse the version number >> from there. I would like to propose a different way to do this. >> SipXsupervisor has access to its build version number, through >> "config/sipxsupervisor-buildstamp.h - SipXsupervisorVersion". So, >> instead of doing the RPM query/parsing, we could pass the >> SipXsupervisorVersion number up to sipXconfig. This method would work >> on developer builds as well. Does anyone see anything wrong with this? > > It's easier than that, I think... > > I believe that you should be able to fetch the process definition file > for any component by doing a GET through sipXsupervisor for it, the same > as reading a log file. If that isn't true, then it's trivial to make it > work. > > Then you can parse the version out of that process definition. Since > that's the value that will be used by the supervisor, it's the most > useful one for sipXconfig to get. >
Ah, I hadn't thought of the process definition files. However, I am looking at them now, and the version numbers in there don't seem to specify the exact revision -- i.e. <version>4.0.2</version> .. The build stamp specifies the revision as well -- const char* SipXsupervisorVersion="4.0.2-016036"; Arjun _______________________________________________ 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/
