Bug 5337 - A Listen address should be passable from the command line
Summary: A Listen address should be passable from the command line
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: All All
: high normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-14 10:39 UTC by Stuart Anderson
Modified: 2018-12-13 22:16 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Stuart Anderson 2005-12-14 10:39:42 UTC
It would be useful to be able to pass in a hostname/IP on which the X Server 
would listen as part of the display specification (ie host:0). This would 
provide more granularity than --nolisten tcp.

The changes for this need to be made where the display is parsed and placed 
intot he global variable "display", which is then used in 
CreateWellKnownSockets() where it is passed into the Xtrans code (via 
_XSERVTransMakeAllCOTSServerListeners()). TRANS(SocketINETCreateListener)() 
also needs to be adjusted to use the hostname passed in instead of INADDR_ANY.

One aspect that needs a little bit more thought, is how to handle non-INET 
transports when a hostname is passed in. Perhaps each transport will just have 
to decide how it wants to intepret (or ignore) the host part of the listener 
address.
Comment 1 Daniel Stone 2007-02-27 01:29:21 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 2 GitLab Migration User 2018-12-13 22:16:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/338.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.