Bug 2126 - Hiveconf errors should not prevent loading other (correct) entries
Summary: Hiveconf errors should not prevent loading other (correct) entries
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: PC Linux
: P2 Normal
Target Milestone: LowPrio
Assignee: Peter Åstrand
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-21 13:20 CEST by Erik Forsberg
Modified: 2024-05-08 10:00 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Erik Forsberg cendio 2006-08-21 13:20:38 CEST 
Currently, if there is a syntax error in a hiveconf file, an exception is
raised. This stops the application doing hiveconf.open_hive, which means that if
the administrator made an error editing file X, applications that really only
needs the information in file Y will cease to function as well. Not good. Also,
it's against the current policy that applications in ThinLinc should run without
hiveconf available (using internal default values).

Need to think about how to solve this.
Comment 1 Samuel Mannehed cendio 2024-05-08 10:00:14 CEST 
It is important to clearly notify the admin of an error. It is common for services to refuse to start if there are errors in the configuration, this is how apache works, for example.
Note You need to log in before you can comment on or make changes to this bug.