On Wed, Feb 27, 2002 at 06:02:33AM -0500, [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
Remove these stupid things, all your system header-files are good. unistd.h, sys/types.h, sys/socket.h, sys/time.h, sys/uio.h etc. Man your functions and you know which ones to include. Further, how do you background your mud and what is the exact message? Edwin -- Edwin Groothuis | Personal website: http://www.MavEtJu.org [EMAIL PROTECTED] | Interested in MUDs? Visit Fatal Dimensions: ------------------+ http://www.FatalDimensions.org/
