Short answer: This has nothing to do with the mud, the server, etc. It is a 'feature' of OpenSSH.
See http://www.snailbook.com/faq/background-jobs.auto.html for a good explanation of what's going on, and what to do about it. Dennis On Wed, 27 Feb 2002 [EMAIL PROTECTED] wrote: > it seems if i try to disconnect while i run my mud my tty isnt closing. it > just puts it as CONNECT_STATE 0, its a linux redhat 7.1 server. just > wondering if anyone out there has had the same problem? it even does it > with stock Rom24b6 base too. i cant figure it out. im realy not fimilar on > how rom actualy creates the socket "port" and how it communicates with the > tty. if someone can fill me in on it maybe i can hack something up. ive > adjusted all my linux config files as so so: > > #if defined(linux) > int close args( ( int fd ) ); > int getpeername args( ( int __fd, __SOCKADDR_ARG __addr, socklen_t > *__len ) ); > int getsockname args( ( int __fd, __SOCKADDR_ARG __addr, socklen_t > *__len ) ); > int gettimeofday args( ( struct timeval *tp, struct timezone *tzp ) > ); > //int listen args( ( int __fd, unsigned int __n ) ); > int read args( ( int __fd, __ptr_t __buf, size_t __nbytes ) > ); > int select args( ( int width, fd_set *readfds, fd_set > *writefds, > fd_set *exceptfds, struct timeval *timeout ) > ); > int socket args( ( int domain, int type, int protocol ) ); > int write args( ( int __fd, __const __ptr_t __buf, size_t > __n ) ); > > #endif > > > this ofcourse only creates 1 conflict and thats listen. so i know that > isnt causing it. doesnt the socket int just looks up the ip addy? > this seems to only happen on redhat 7.1 and 7.2 though but it may work on > other redhats 7.1 7.2 ive only tried it on this box. i fired up zip slack > 8.0 and it worked fine. maybe some out of the ordianary linux bug? > anyhow give me a should about this. this is diffently interesting. > ohh im running if off ssh telnet port is closed. somebody with redhat 7.1 > try to ssh in and run the mud then exit? itll be interesting if you get > the same results. ohh my ssh version is: > > SSH-1.99-OpenSSH_2.5.2p2 > > > >
