On Windows I follow these steps:
- in admin console: closing all hosted files
- stopping FMServer in admin console
- in Windows Services stopping FileMaker Server
On MacOS first 2 steps same but 3. I am using the Terminal to run: sudo service fmshelper stop
is this the way to do it or am I missing something?
Thank you!
sudo launchctl stop com.filemaker.fms
Also check your Activity Monitor before shutting down. Search for "fm" to limit to fms related services.
If you need to restart from the terminal, use the same sudo command as above, with start instead of stop.
2 Likes
Great thanks! So all could be done via Terminal. Will see if I can figure out how to use a Terminal script to automize this or would that be not graceful for shutting down? I thought of a sequence closing all files then testing if all closed then proceeding with terminating all involved?
if you find a reliable way of determining when FMS has completed shutdown, so that it can be issued the start command, I'd be interested. I've been failing to get a shell script to do this accurately for a long time. I've resorted to a long pause which gets the job done but it annoys me that I don't have a better way.
1 Like
In case it's of use to someone, here's a PDF file with the FMSAdmin Command Line commands. It can be gathered from within Terminal as well, of course (fmsadmin HELP [OPTIONS]), but I like having it as a document. This is from FMS v16, but it's basically the same.
fms16_cli_help.pdf (210.6 KB)
4 Likes
This is very helpful indeed @daleallyn. I wish the FileMaker documentation would be as it was years before. Now it misses out IMHO. THANK YOU!