Note The sudo command requires you to authenticate. your primary goal is to prevent the databases from being corrupted as a result of a power loss. Along with the script name and the parameter, you can specify to Wait for Completion. It is not supported in Runtimes, and it doesn’t make sense in Server schedulesscheduled scripts already perform on the server. 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 Perform Script on Server (P.S.O.S., as FileMaker devs like to call it) works in FileMaker Pro, FileMaker Go, and WebDirect. You must be logged in to the machine where FileMaker Server is running. To start or stop FileMaker Server manually: Note The CLI is available via the command prompt (Windows) and the Terminal application (OS X). You must be logged on to the computer running FileMaker Server, either directly or using remote desktop software, to use the CLI.
Stop filemaker server command line windows#
EXE: Start/stop/restart any Windows Service from the command line The Core. FileMaker provides the tool fmsadmin for administering FileMaker Server via the command line interface (CLI). Close all database files before stopping FileMaker Server processes. net stop FileMaker Server, link, Starting or stopping the FileMaker. 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. See Using the command line interface for the fmsadmin start and fmsadmin stop commands. If the Admin Console is not responding, you will have to stop the FileMaker server via the command line. If this default configuration has been changed, manually turn the FileMaker server back on. Table 25.1 contains a list of all the commands and options you can use with fmsadmin. Instead, it refers you to the online help. After the machine has restarted, your FileMaker server will most likely turn on automatically. The FileMaker Server documentation doesn document the command line syntax very well (an odd lapse in whats otherwise a very good document).
For example, after you restrict access to Admin Console (on the Administration tab), you must restart all FileMaker Server components. When the server has stopped, restart your machine. 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)
0 kommentar(er)
