"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > If you check wait_timeout value using mysql command-line client, it > > takes value for 'wait_timeout' from 'interactive_timeout' variable > > which is 28800 by default. > > thanks, now i see. > this behaviour is rather strange, isn't it? why are there two different > variables then? i thought that wait_timeout is for non-interactive and > interactive_timeout for interactive clients. > > when i run: > mysql -e 'show variables;' > then i get right value (=30), as i set it on startup. > > when i start mysql command line client and run: > show variables; > then i get value for interactive_timeout (it's default =28800). > > } this is what you pointed out. > > but when i run: > mysql -e 'set wait_timeout=26600;' > mysql -e 'show variables;' > then i get old values: > wait_timeout=30 > interactive_timeout=28800
Because you set session variable and SHOW VARIABLES display values for global variables. Use GLOBAL keyword in the SET statement. shell> mysql -e "SET @@GLOBAL.wait_timeout=26600" > > this behaviour is quite odd and i don't see a way how to set > wait_timeout for non-interactive clients from interactive session. > (i suppose that mysql command line client is non-interactive when it > runs with the "-e" parameter) > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]