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.
