SyncoveryCL start remains in foreground on Macs...

[phredd]

I've been able to programmatically set up a properly configured profile using SyncoveryCL, but I've been unable to use it to launch the scheduler without console output grabbing the foreground of a terminal session. Further, escaping the console after launching the scheduler causes the scheduler to shut down.

I've looked and there doesn't seem to be an active LaunchDaemon or LaunchAgent entry for Syncovery even when the scheduler is up and functioning. I do see entries for Syncovery when I use launchctl list, though: application.com.company.Syncovery.766576162.766576167

Any suggestions for properly launching the scheduler from a script on a Mac?

[tobias]

Hello,
there are two different schedulers to choose from:

a) the background scheduler, which is an app: BackgroundScheduler.app hidden inside the Syncovery bundle. You can start it like any other app:

Code: Select all

open /Applications/Syncovery.app/Contents/MacOS/BackgroundScheduler.app

b) the service scheduler. This must be chosen and installed on the Scheduler tab sheet in Syncovery. It will copy SyncoveryCL to the PrivilegedHelperTools and rename it to SyncoverySRV. I think you can start and stop that like any other daemon.

[phredd]

Thanks!

I'm opting to launch the background scheduling app via launchctl.