Bug 4085 - Too easy to restart VSM with unsaved config changes
Summary: Too easy to restart VSM with unsaved config changes
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Administration (show other bugs)
Version: 3.2.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Pierre Ossman
Depends on:
Reported: 2011-12-05 13:05 CET by Peter Åstrand
Modified: 2022-07-07 09:31 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2011-12-05 13:05:13 CET
Doing this:

* Going to /vsm/agent

* Filling in a custom agent_hostname

* Stopping vsmagent. Starting vsmagent. 

In this case, vsmagent has been restarted with the old agent_hostname configuration, even though the new one is displayed on the screen. This is because the user has not clicked on Save. 

Probably hard to find a good solution to this. Pierre is suggesting that the service start/stop should perhaps be on a different page.

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