Feature #2475
Reserve a VNC port number
| Status: | Closed | Start date: | 11/19/2013 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 5.0 | |||
| Resolution: | fixed | Pull request: | 
Description
To avoid collisions with well known services in the virtualization host.
Related issues
History
#1
     Updated by Jaime Melis over 7 years ago
    Updated by Jaime Melis over 7 years ago
    - Assignee set to Jaime Melis
- Target version changed from Release 4.6 to Release 4.8
#2
     Updated by Ruben S. Montero about 7 years ago
    Updated by Ruben S. Montero about 7 years ago
    - Tracker changed from Feature to Backlog
- Status changed from New to Pending
- Assignee deleted (Jaime Melis)
- Priority changed from Normal to High
- Target version deleted (Release 4.8)
#3
     Updated by Ruben S. Montero over 6 years ago
    Updated by Ruben S. Montero over 6 years ago
    - Related to Feature #2980: Improve management of the VNC Port Range added
#4
     Updated by Ruben S. Montero almost 6 years ago
    Updated by Ruben S. Montero almost 6 years ago
    - Duplicated by Bug #3885: Failed to start VNC server... socket bind failed: Address already in use added
#5
     Updated by Ruben S. Montero over 5 years ago
    Updated by Ruben S. Montero over 5 years ago
    - Tracker changed from Backlog to Feature
- Status changed from Pending to Closed
- Target version set to Release 5.0
- Resolution set to fixed