Hello John, What platform on you running it on? According to the source the this is a call failing on setting stdout with setsockopt, could your OS not let socket options happen on stdout (and did pretend that you are on linux?)? What does the inetd.conf entry look like? Could stdout have been closed by something (like the tcp wrapper daemon or ?)? I'm not sure if this have the same behavior.
Take Care, -------- Lee Carmichael Service Architect - WorkSpace WAM!NET a Division of SAVVIS Communications, Inc. 655 Lone Oak Rd Building A Eagan, MN 55121 ph# 651-256-5292 email: [EMAIL PROTECTED] On Wed, 24 Sep 2003, John Hally wrote: > I think I have this set up correctly, but here's what I'm getting for errors > when trying to use a client to connect thru the proxy: > > Sep 24 15:24:48 [hostname] ftp.proxy[2143]: can't set TCP_NODELAY, error= > Socket operation on non-socket > Sep 24 15:24:48 [hostname] ftp.proxy[2143]: -ERR: can't get client info: > Socket operation on non-socket > > any ideas? > > thanks > > > --general-l------------------------------------ > To unsubscribe please visit: > http://www.ftpproxy.org/html/maillinglists.html > --general-l------------------------------------ To unsubscribe please visit: http://www.ftpproxy.org/html/maillinglists.html
