# config file does not work as expected

**URL:** <https://forums.percona.com/t/config-file-does-not-work-as-expected/6174>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [February 5, 2018, 8:18am UTC](https://forums.percona.com/t/config-file-does-not-work-as-expected/6174 "2018-02-05T08:18:47Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![scott.nemes](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/scott.nemes/32/5_2.png) [@scott.nemes](https://forums.percona.com/u/scott.nemes)\
**Post date:** [February 6, 2018, 4:27pm UTC](https://forums.percona.com/t/config-file-does-not-work-as-expected/6174/5 "2018-02-06T16:27:01Z")

</div>

Hi cwhsu;

Yeah that’s odd. I tested it out locally and am able to set both individually. Basically the wait\_timeout variable is for non-interactive connections, and interactive\_timeout is for interactive connections. Would be interesting to see if there is an XtraDB-cluster specific reason for it.

Otherwise I’d try setting wait\_timeout directly in /etc/my.cnf or /etc/mysql/my.cnf under the [mysqld] tag to see if it happens to pick it up that way. Still seems likely there is an option file issue going on there somewhere.

---

_[View the full topic](https://forums.percona.com/t/config-file-does-not-work-as-expected/6174)._