restchip.blogg.se

Note The sudo command requires you to authenticate. Open the Linux CLI and enter the start or stop command:įileMaker Server only: sudo service fmshelper startĬlaris Server only: sudo service claris startįileMaker Server only: sudo service fmshelper stopĬlaris Server only: sudo service claris stop You must be logged in to the machine where FileMaker Server is running. To start or stop FileMaker Server manually: Admin Console allows you to start and stop the Database Server, the FileMaker Data API Engine, the OData API Listener, the Web Publishing Engine on a FileMaker WebDirect primary or secondary (FileMaker Server only) machine, and the XDBC Listener (FileMaker Server only) individually without restarting the primary machine. Close all database files before stopping FileMaker Server processes. Starting or stopping FileMaker Server components. Warning File corruption may occur if you stop FileMaker Server processes when database files are open on the host. If you choose not to have the FileMaker Server processes started during Linux startup or if you stopped the processes, you can start them again manually. Typically, the FileMaker Server processes are started when the machine is started. In a multiple-machine deployment (FileMaker Server only), FileMaker Server processes run on each machine. In Linux, FileMaker Server runs as several background processes that start when FileMaker Server is installed. You do this either by restarting the machine or by restarting the FileMaker Server processes. For example, after you restrict access to Admin Console (on the Administration tab), you must restart all FileMaker Server components. There may be times when you need to start or stop all components of FileMaker Server on a machine.

Starting or stopping FileMaker Server background processes (Linux)