There is no "Push" on the part of the server.

A server restart does not effect client changes.

A client restart or a start of an application on the part of the client effects a synchronization.

Note Only if changes are older than 60 seconds, a synchronization is performed. So when a change on the server has been performed, you have to wait a minute for a client test.

In order to be sure that a running application will get the change, it has to be restarted.

The waiting time of 60 seconds is hard coded and cannot be changed.

There is no difference if a change has been made by PARTadmin or by copying/removing directly on the sitesetup. Only the change on the disk is decisive. PARTadmin has no special way.

The modification date and the number of files are saved under $CADENAS_USER\rfs\state.json saved.

Example entry in state.json

{"$CADENAS_SITESETUP":{"modified":"2023-10-26T04:13:33Z","fileCount":16},"$CADENAS_SETUP":
 {"modified":"2023-10-26T04:13:33Z","fileCount":511}}

The Sync is performed for the specific path, e.g. SITESETUP or SETUP. For an unchanged number of files the specific changes will be synced; if the number of files changed, everything is synced.