[MUD-Dev] Re: Quick socket question

J C Lawrence claw at kanga.nu
Sat Nov 7 20:02:27 CET 1998

On Sat, 7 Nov 1998 15:06:42 -0600 (CST) 
Cat <cat at bga.com> wrote:

> Well, we were going to install Solaris 86 on the Furcadia server
> machine to replace the buggy older version of BSDI it had on it.
> But the sysadmin out there suggested going to Red Hat Linux instead,
> because it's a BDS family rather than a SYSV family, and there might
> be fewer problems.  

Linux is actually very POSIX/SysV (ouside of Slackware).  

> I agreed.  I don't know how hard getting it going on SYSV would have
> been, but I know my O'Reilly "Using C on the Unix system" is so old
> that it says Berkeley Unixes have sockets and SYSV don't!  

Quite simply: everybody has sockets now, They are literally universal.

> Surely SYSV has to have sockets now, what with this "internet" thing
> having gotten so popular since this book was written - don't they?


> Anyway, I got a couple compatibility problems involving select() and
> accept() worked out, but I've noticed the return of a problem we
> sometimes had under Linux with the old DragonSpires server, which is
> the ancestor of the Furcadia server code.  After the game is shut
> down or the server code crashes, and it tries to restart, it fails
> to bind the port for the next 15-20 minutes.  

Yes.  This is very very standard and actually even predictable.  The
exact causes (and I think the handling) are well documented in
Steven's TCP/IP books (which are roughly 50 miles south of me right
now, at work).  Translation: Its in the book, I don't remember the
details, I'll look it up on Monday if nobody does it before me.

J C Lawrence                               Internet: claw at kanga.nu
----------(*)                             Internet: coder at kanga.nu
...Honourary Member of Clan McFud -- Teamer's Avenging Monolith...

More information about the mud-dev-archive mailing list