C:\Users\username\Documents\Xibo Library 120 300 C:\Program Files\Xibo\XiboClient.exe log.xml ``` The important part of the above configuration file is the settings between the `` element. ### Client Library The library location as configured in the Player. ### Polling Interval How often the watchdog should check for application activity. ### Threshold The threshold in seconds that the application has to be inactive before the watchdog will restart it. ### Process Path The fully qualified pathname to the application EXE that should be monitored. This will be used to restart the application when it is detected as being inactive. ### Log File Name This is the name of the log file as configured in the Player that is being monitored. Downtime events and restarts will be added to the end of the usual error log. ## Start with Windows A short cut to the watchdog EXE should be created and added to the Windows start up program group in the Start Menu. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.xibosignage.com/setup-docs/open-source-player-apps/xibo-for-windows-installation/windows-player-watchdog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.