MySQL Bugs: #24376: wait_timeout affects socket connections

Bug #24376	wait_timeout affects socket connections
Submitted:	16 Nov 2006 23:54	Modified:	19 Dec 2006 17:33
Reporter:	Adam Donnison	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	4.1,5.0	OS:	Linux (Linux)
Assigned to:	Paul DuBois	CPU Architecture:	Any
Tags:	configuration, server, socket, wait_timout

Description:
According to the documentation wait_timeout should only affect tcp connections, however if you set wait_timeout then it also times out idle socket connections.

How to repeat:
set wait_timeout to a low value (30 seconds, e.g.) and start a connection using either the C-API or a scripting language such as PHP.

Connections to 127.0.0.1 using tcp will time out.
Connections to localhost using unix domain socket will time out (which according to the documentation it shouldn't).

Suggested fix:
Either make it do what the documentation suggests it should or change the documentation.

http://dev.mysql.com/doc/refman/4.1/en/server-system-variables.html

  This timeout applies only to TCP/IP connections, 
  not to connections made via Unix socket files, 
  named pipes, or shared memory.

TCP and Unix Domain sockets are handled by the same code
so wait_timeout applies to both.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.