MySQL Bugs: #5302: Window server can start in unusable state

Bug #5302	Window server can start in unusable state
Submitted:	30 Aug 2004 21:16	Modified:	16 Feb 2005 11:13
Reporter:	Paul DuBois	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	All non-nt servers	OS:	Windows (WIndows)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
A while back I pointed out that if you start a Windows server with
--skip-networking but don't enable some other connection interface,
the server starts but cannot be used. (You cannot connect to it.)

I checked into this again today and I see that some progress has been
made.

If you start mysqld-nt or mysqld-max-nt with --skip-networking, the
server correctly senses that it cannot accept connections and prints
this message:

  TCP/IP,--shared-memory or --named-pipe should be configured on NT OS

Then the server exits.

However, the non-nt servers all will start up in an unusable state.
It would be better for them to print a message and exit.

How to repeat:
See above.

Thank you for the bug report I was able to repeat.

This bug seems to be fixed long ago,
Miguel just forgot to close it. Closing.