Bug 1237 - Admin isn't informed of bad hiveconf settings
Summary: Admin isn't informed of bad hiveconf settings
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: PC Linux
: P2 Minor
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
Depends on:
Reported: 2005-04-01 10:26 CEST by Peter Åstrand
Modified: 2022-04-05 13:27 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2005-04-01 10:26:47 CEST
Currently, we more or less "trust" the configuration files to contain "sane"
values. For example, if you change /vsm/tunnelslots_per_session to -42, VSM
would probably crash and/or fail. 

We should go through our Hiveconf files, check where the parameters are used,
and, if necessary, add input data validation. 

This bug is also related to the famous Hiveconf "metadata support" feature. The
plan is to have Hiveconf support metadata, which can contain information about
which values are allowed etc.
Comment 1 Peter Åstrand cendio 2005-04-01 10:28:49 CEST
One thing to consider: Should the rangecheck be done when, say, vsmagent starts
up, or scattered through out the code (say, in find_free_display)?

Note You need to log in before you can comment on or make changes to this bug.