Bug 5534 - Confusingly similar /vsm/vsm_listen_port and /vsmserver/listen_port
Summary: Confusingly similar /vsm/vsm_listen_port and /vsmserver/listen_port
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Peter Åstrand
URL:
Keywords:
Depends on:
Blocks: 571
  Show dependency tree / graph
 
Reported: 2015-05-19 13:13 CEST by Karl Mikaelsson
Modified: 2023-05-09 13:22 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:

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

Description Karl Mikaelsson cendio 2015-05-19 13:13:29 CEST 
Right now there's two configuration variables that states which server port the vsmserver is supposed to listen to - /vsm/vsm_server_port and /vsmserver/listen_port.

When trying to communicate with vsmserver, some code looks at the parameter in /vsm and other code looks at the parameter in /vsmserver, so there's not a clear split for client and server code either.

There might be a reason to why this is the best option but the documentation is poor, just stating that /vsmserver/listen_port should normally be set to the same thing as /vsm/vsm_server_port.


The same problem exists for /vsmagent/listen_port and /vsm/vsm_agent_port.
Note You need to log in before you can comment on or make changes to this bug.