•Run after profile: To have a program run after the profile has finished,enable the Run after profile checkbox and type the name into the edit-box or click the folder icon next to it. You can use the same variables and switches as per the Run Before program.
|
Windows has many restrictions on how programs can react to and handle the shutdown or restart of a computer. Due to these restrictions Run Before and Run After programs will silently fail and not even start if the profile is set to run on shutdown/logoff and the computer is shutdown or restarted (the programs will still be run as per normal if its a logoff).
The special variable %PROFILEFAILED% can be used to pass the result of the profile run. If the value is 1 (one) then the profile failed (or was aborted), if the value is 0 (zero) then the profile run was a success. |
•Wait until the program has finished before running next profile or exiting: If this option is enabled, then when the program is run, SyncBackPro will pause and not finish the profile until the program has finished. The program must exit/close before the profile will complete running. If you do not enable this option then the program will be run and the profile finish as per normal without waiting.
•Wait for a maximum of...: If this option is enabled, then you can choose how long SyncBackPro should wait for the program to finish before the profile run ends. If the program does not finish within the specified time then SyncBackPro will end the profile run. Note that it is advisable to set a maximum waiting time otherwise SyncBackPro may get "stuck" waiting for a program that is not going to exit.
•Run the program even if the profile fails: Select this option to run the after program even if the profile fails. By default the program is not run if the profile fails, e.g. a file could not be copied. If the source or destination is a UNC path (\\server\share\folder\), and it cannot be connected to, then the Run After program is not run.
oOnly run the program if the profile fails: If you only want the program to run if the profile fails, then select this option.
•Run the program when simulating: By default the program is not run when doing a simulated run. This is advisable as the program may change or delete files, which is not something you generally want to do during a simulated run.
•Run the program after the log file has been closed (any failure will not be recorded in the log): By default the after program is run before the log file is closed and created. This is so the result of the program run can be recorded. It also means the log file has not yet been created. In some situations you may want the after program to use the log file, and if so, you need to enable this option. The variable %LOGFILENAME% can be used to get the filename of the first page of the log file.
•Run the program only if any file changes were made: If you only want the program to run if any files were copied, deleted, or moved, then tick this option.
•Read stdin from the following file (console programs only): If you are running a console (command line) program, then you can send input to the program from a file. Note that you cannot send input to a Windows graphical program, only console programs. Variables can be used for the filename. See the next setting for an example.
•Record stdout in the log file (console programs only): If you are running a console (command line) program, then you can record output from the program in the log file. Note that you cannot get the output from a Windows graphical program, only console programs. If you do not use the setting Wait until the program has finished then the output written to the log may be incomplete or impossible to retrieve. As an example of using stdin and stdout: set the run after command to "%CSIDL_SYSTEM%sort.exe", set the stdin filename to %CSIDL_SYSTEM%sort.exe, and enable the option to record stdout. Click the Test button.
All Content: 2BrightSparks Pte Ltd © 2003-2024