Re^2: Could not create socket: Bad file number

Actually, the LocalHost line should be removed entirely unless there is a desire to bind to a particular interface (which is very rare). That shouldn't cause that problem, though.

Comment on Re^2: Could not create socket: Bad file number Download Code

Replies are listed 'Best First'.
Re^3: Could not create socket: Bad file number by Joost (Canon) on Aug 30, 2007 at 21:18 UTC
Exactly. Just to emphasize; you (usally) only need the LocalHost argument if you have multiple network connectors on your machine and you only want to listen on one of them. If you do need to do this, it may be easier to specify the IP address instead of the host name, since that may be easier than configuring the right hostname(s) to the right port(s) "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^4: Could not create socket: Bad file number by perlofwisdom (Pilgrim) on Aug 30, 2007 at 21:45 UTC
I removed the LocalHost argument -- no change. Are there Unix settings that need to be in place for Socket communications to work properly? i.e. maybe that port is blocked?	[reply]