On Sun, Jan 02, 2000 at 01:29:33AM -0800, Mark Maggelet wrote: > @40000000386f36191f0ac50c tcpserver: fatal: unable to bind: address already used > I'm getting tons of these lines in my logs, what would cause it? > what port is tcpserver trying to bind to? Do some more work for us, we aren't clairvoyant. It appears that another tcpserver is running already. Perhaps you invoked one by hand and then made svscan/supervise scripts. Try and figure out what tcpservers and running, and who's their parent. Regards, bert. -- +---------------+ | http://www.rent-a-nerd.nl | nerd for hire | | +---------------+ | - U N I X - | | Inspice et cautus eris - D11T'95
- tcpserver: fatal: unable to bind: address already used Mark Maggelet
- Re: tcpserver: fatal: unable to bind: address alre... bert hubert
- Re: tcpserver: fatal: unable to bind: address alre... Andy Bradford
- tcpserver: fatal: unable to bind: address already ... Philip Tong
- RE: tcpserver: fatal: unable to bind: address ... Brett Randall
- Re: tcpserver: fatal: unable to bind: address ... Dave Sill
- tcpserver: fatal: unable to bind: address already ... Jon
- Re: tcpserver: fatal: unable to bind: address ... Kris Kelley
- Re: tcpserver: fatal: unable to bind: address ... Charles Cazabon
- tcpserver: fatal: unable to bind: address already ... Alex Tsang
- Re: tcpserver: fatal: unable to bind: address ... Chris Johnson
- Spam Removal Jeremy Suo-Anttila