Hello Gary,
Thank you for your quick answer. I thought that current running values would
be reflected in this page.
May I suggest adding a message to the "configure startup options" page that
would say something similar to:
"Options passed to ntop by CLI arguments are not reflected here" ?
Regards,
Marc.
le 10-07-16 12:01, Gary Gatten à [email protected] a écrit :
> Any options set in the GUI are stored in a DB. Options specified at startup
> (on the cli, script, whatever) aren't copied to the DB, so the GUI knows
> nothing about them - and hence yes, displays default values.
>
> If you want, I guess you can take all the startup options off and specify them
> only in the GUI. I'm not sure which ones would over-ride which... I suspect
> CLI args take precedence, but not sure.
>
> The "resolved to" Is what matters - those are the args that ntop ultimately
> processed and is currently using.
>
> G
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Marc Mazuhelli
> Sent: Friday, July 16, 2010 10:52 AM
> To: [email protected]
> Subject: [Ntop] Configure startup options: default values show instead of
> current values?
>
> Hello,
>
> In my recent ntop 3.4-pre3 installation, I have noticed that when I go to
> Admin => Configure = Startup Options, many of the options I started ntop
> with don't appear. For example, I have the following options in my startup
> script:
>
> -https-server 3001 --track-local-hosts
>
> (they correctly appear in "Resolved to..." in the "About => Show
> configuration" page) but in the "Configure startup options" page, HTTPS
> Server (-W) shows up as 0 and Track Local Hosts (-g) appears as "No".
>
> It's as if default values are show instead of the current values.
>
> Is there a way to fix this?
>
> Thanks,
> Marc.
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
