#11 Copyover Problems

[Anonymous]

I have found problems with the copyover system in
firstmud 4.4 codebases

the problem has to do with the control and port numbers.

When the mud returns from a copyover, the control is
being set to "0", which causes a socket error if someone
tries to connect to the mud.

The error which comes up is: socket operation on a non-
socket.

Now I fiddled round to see what control is being set to
and such when the mud reboots, and found that where
it checks for the "-c" argument with the execution, to
set it to look for argv[3] stead of argv[pos++] seems to
clear the problem up.

------------------

now what I believe is going is, your feeding the
execution name as one of the arguments when you run
a copyover, this dealing with cygwin and windows based
terminals, to deal with the binary file... however on unix
based systems, your not doing anything there, so
instead of getting to the control, your getting to "rom",
which just makes control = 0, and BAM, blow up time..

Just thought I'd post this in... you could simply just
incrase pos by 1, when your dealin with a UNIX based
platform that doesn't need all that hocus pocus about
the binary file.

[Nobody/Anonymous]

Logged In: NO

you could change argv[pos++] to argv[++pos] instead,
that would work too.