From: Robert Klemme Date: 2008-10-14T15:30:05+09:00 Subject: Re: Problem with bind for Socket class On 14.10.2008 07:47, Vladimir Fekete wrote: > when I tested it it worked. But when I tried to run it again I've got error > message: > > /t1.rb:10:in `bind': Address already in use - bind(2) (Errno::EADDRINUSE) > from ./t1.rb:10 > > I tried to find "related" bug/problem in google but withouth success. Could anybody > help me how to "unbind" socket ? Or explain me where I making mistake. I have > some experiences only with WinSock API and I don't remember any unbind function. > P.S. I'm running it on Debian Linux, Ruby version 1.8. I remember that on some OS (or particular versions) socket cleanout is delayed. Did you try to check with "netstat -a -n | fgrep 2201" or similar to see what state the port is in? Cheers robert