Re: Hamm Bug Stamp-Out List now on www
Raul Miller <rdm@test.legislate.com> writes:
> I chouldn't find much documentation on the chooser -- why it needed
> xdm to listen to some random port. The best documentation I could
> find was the xdm man page, and it didn't say much on the topic of
> non-local choosers. My guess is that this was written this way
> because some operating systems don't have pipes, and this code
> was written to be portable to very sludgy systems.
> Looking at the source, in choose.c there's ProcessChooserSocket
> which seems to be the only thing that deals with traffic on
> this socket. It pulls some address information out and calls
> RegisterIndirectChoice... I suppose I could delve further, but
> since maybe my time would be better spent grepping through
> the x books...
> Does any of this ring a bell? Am I completely wasting my time?
The chooser does a broadcast asking for available xdm servers, and
puts them into a list for the users. I've guessing that the socket is
there to receive the results of the broadcast. (It's UDP, right?)
IIRC, machines continue to show up in the list after it becomes
visible on the screen. (So the port has to remain open at least as
long as the chooser is visible.)
Steve
dunham@cps.msu.edu
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: