When Linuxconf receive an HTTP request, it will start to process the request and will stay running for some time. After a period of inactivity equal to the timeout, Linuxconf will exit. While this has little impact on its functionality because the HTTP protocol is logically stateless (each transaction is conceptually complete), there exist some complex HTML dialogs which require Linuxconf to remember information about pages it has generated. If you are too slow to fill a screen and accept it, Linuxconf may very well quit in the mean time. This has two drawbacks:
Using this feature you can raise the timeout so Linuxconf will wait longer before exiting. The timeout is expressed in minutes.