At 6:29 AM -0700 2000-03-22, sasha@stripped wrote:
>Pablo Prieto wrote:
>>
>>
>> > I am by far not an NT expert, but I've heard that interesting
>>things can happen
>> > when you try to listen on a port that someone is already
>>listening on - in any
>> > case, you should not be starting a second instance of a daemon,
>>like Miguel said
>> > earlier in Spanish.
>>
>> Yes, it's true. But the second instance is from the client program, not
>> the daemon. I guess the problem were with the locks in the tables, sice
>> they weren't "OPTIMIZE TABLE"'ed, as you said.
>>
>> Thanks a lot for your help!
>>
>> BTW, I hardly remember it, but I think it was a error, raised by the
>> Win32 TCP-IP library, to open a connection in listening mode if someone
>> else was listening to this port. If this is the way it would be
>> impossible to have two instances of a service like MySQL running at the
>> same time (anyrod, doing it sounds pretty odd).
>>
>> Pablo.
>>
>> --
>
>No, connection from a client should be no problem - the problem will happen if
>you try to start two instances of the server and have them listen on the same
>port. Under Unix, this will result in a error from the second one,
>and will not
>affect the first. I am not sure what would happen on NT.
>
>
>--
>Sasha Pachev
Anyone know what happens on NT? I'd be surprised if you could start
two things on the same port, but then again, we're talking about NT
here. :-)
--
Paul DuBois, paul@stripped
