Bug #4900 Client Tools and Client Library start options
Submitted: 4 Aug 2004 23:07 Modified: 27 Jun 2007 15:25
Reporter: Miguel Solorzano Email Updates:
Status: Won't fix Impact on me:
Category:MySQL Server Severity:S4 (Feature request)
Version:4.0 OS:Windows (Windows)
Assigned to: CPU Architecture:Any

[4 Aug 2004 23:07] Miguel Solorzano
The server can be started with the below start options:

c:\mysql\bin>mysqld-nt --standalone --console --skip-networking --enable-named-pipe --skip-name-resolve
040804 17:55:42  InnoDB: Started
mysqld-nt: ready for connections.
Version: '4.0.20a-nt'  socket: ''  port: 0

The above is for to avoid the  Winsock Windows initialization and the DNS
lookup  and to work locally  exclusively with named pipes.

However a client like mysqladmin doesn't has the same start options for
to get the same functionality so the Winsock is initialized  for example:

c:\mysql\bin>mysqladmin -uroot --pipe ping
mysqld is alive

It is possible to have the start options:


for Client tools shipped with release packages or applications compiled
against the libmysql.dll or mysqlclient.lib ?

How to repeat:
see description

Suggested fix:
[4 Aug 2004 23:14] MySQL Verification Team
Changing for feature request.