# launchd ExitTimeOut and graceful stop discipline for large MLX models > ExitTimeOut zero is interpreted as infinity, and the man page says it should not be used because it can stall system shutdown forever. Parent: [Mac local LLMs: Serving ops and multi-model](https://llms-explorer.com/tree/mac-local-llms-serving-ops-and-multi-model/) · 2 facets · 4 facts · page: https://llms-explorer.com/tree/launchd-exittimeout-and-graceful-stop-discipline/ ## Facts - ExitTimeOut zero is interpreted as infinity, and the man page says it should not be used because it can stall system shutdown forever. — [source](https://keith.github.io/xcode-man-pages/launchd.plist.5.html) - A plist for a 400 GB-class MLX server should set ExitTimeOut explicitly rather than rely on any default. — source: `asserted` ## Corrections and disagreements - CONTRADICTS launchd-service-setup-for-local-llm-servers.md line 53 (ExitTimeOut defaults to 20 s): launchd.plist(5) says only that the default value is system-defined. — [source](https://keith.github.io/xcode-man-pages/launchd.plist.5.html) - CONTRADICTS omlx-fatal-teardown-watchdog-and-wired-memory-st.md ("default 5 s launchd kill window"): the man page names no 5 s default; the figure is the issue reporter's observation, not a documented value. — [source](https://keith.github.io/xcode-man-pages/launchd.plist.5.html)