[omniORB] Unable to set 'scanGranularity' and 'in/outConScanP eriod' paramet ers via command line

Burton, Craig CBurton at verisign.com
Wed Jun 2 16:27:22 BST 2004


Thanks, Duncan.  I found the cause with a quick check of omniORB source:  lcdMode was being set to true in the config file, overriding the parameters I mention below (and a few others).


Craig

-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org] 
Sent: Wednesday, June 02, 2004 7:37 AM
To: Burton, Craig
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] Unable to set 'scanGranularity' and 'in/outConScanPeriod' paramet ers via command line 


On Friday 28 May, "Burton, Craig" wrote:

> We're using omniORB 4.0.2 on Solaris and I am unable to see the
> command-line configurables 'scanGranularity', 'inConScanPeriod' and
> 'outConScanPeriod' via the command line like the following:
>
> my_process_name -a my_arg -ORBscanGranularity 5 -ORBtraceLevel 40
> -ORBinConScanPeriod 3600 -ORBoutConScanPeriod 3600
>
> When I look at the process output, I see that the "trace level"
> argument was set, but the other's weren't.
>
> Is it possible to set the three configurables as I've attempted, or
> must I build the 'options' array for ORB_init?

It works fine for me on the command line. The only way I can imagine
it wouldn't work would be if you override it in the options array in
ORB_init.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --



More information about the omniORB-list mailing list