Commandline usage
-
- Posts: 12
- Joined: Tue Jul 14, 2020 5:40 pm
Commandline usage
Hello,
I'm having a bit of trouble with command line usage. I would like to do the following....
I would like to run a profile named "Test1" that is within a config file that I exported from syncovery. The config file is named "t.xml".
I have attempted using the command line arguments (one per line here for clarity)
"c:\program files\syncovery\syncoverycl.exe"
/INI="<MypathToConfigFile>\t.xml"
/RUNX="Test1"
/M
/P
/LEFT="JobDrive:\Jobs"
/RIGHT="BackupDrive:\Jobs"
The output informs me that it "Could not load profile Test1"
I am confident that my profile Test1 is inside of the file t.xml as I have looked inside. Any suggestions as to what I am missing?
I'm having a bit of trouble with command line usage. I would like to do the following....
I would like to run a profile named "Test1" that is within a config file that I exported from syncovery. The config file is named "t.xml".
I have attempted using the command line arguments (one per line here for clarity)
"c:\program files\syncovery\syncoverycl.exe"
/INI="<MypathToConfigFile>\t.xml"
/RUNX="Test1"
/M
/P
/LEFT="JobDrive:\Jobs"
/RIGHT="BackupDrive:\Jobs"
The output informs me that it "Could not load profile Test1"
I am confident that my profile Test1 is inside of the file t.xml as I have looked inside. Any suggestions as to what I am missing?
Re: Commandline usage
Hello,
the /INI command line parameter can only refer to a .ini file, not XML.
XML files can only be imported to an ini file but not be run directly.
You could export your profile in .ini format instead, or just keep it in your main Syncovery.ini file and leave the /INI= parameter away.
the /INI command line parameter can only refer to a .ini file, not XML.
XML files can only be imported to an ini file but not be run directly.
You could export your profile in .ini format instead, or just keep it in your main Syncovery.ini file and leave the /INI= parameter away.
-
- Posts: 12
- Joined: Tue Jul 14, 2020 5:40 pm
Re: Commandline usage
I see.
I need to be able to manipulate the ini file in advance, but it appears to contain binary information and not just text. Does the .ini file contain binary?
I need to be able to manipulate the ini file in advance, but it appears to contain binary information and not just text. Does the .ini file contain binary?
Re: Commandline usage
Hello,
yes, the INI file is binary and most profile settings can't be edited. In this case you may need two commands, for example:
The /M parameter means "minimize" and does not have any effect with the SyncoveryCL command line tool.
yes, the INI file is binary and most profile settings can't be edited. In this case you may need two commands, for example:
Code: Select all
SyncoveryCL.exe /IMPORT="your xml file"
SyncoveryCL.exe /RUNX="Test1" /P /LEFT="JobDrive:\Jobs" /RIGHT="BackupDrive:\Jobs"
-
- Posts: 12
- Joined: Tue Jul 14, 2020 5:40 pm
Re: Commandline usage
Understood.
So in summary, if we use INI files they cannot be edited. They can be run using a combination of /INI= and RUNX in a single commandline.
If we use XML, they can be edited, but must be imported in one commandline and RUNX executed in a second commandline.
Is there a flag for the commandline arguments to do a "test" or "preview" that lists the pending changes without having to actually perform the sync/backup?
So in summary, if we use INI files they cannot be edited. They can be run using a combination of /INI= and RUNX in a single commandline.
If we use XML, they can be edited, but must be imported in one commandline and RUNX executed in a second commandline.
Is there a flag for the commandline arguments to do a "test" or "preview" that lists the pending changes without having to actually perform the sync/backup?
Re: Commandline usage
Hello,
you can try
/RUNI="Profile Name"
to run a profile interactively, including the ability to export an HTML page of the files to copy ... but if you wanted interactive, you should probably better run the job in the Syncovery GUI ... so I am not sure what your exact requirement is.
you can try
/RUNI="Profile Name"
to run a profile interactively, including the ability to export an HTML page of the files to copy ... but if you wanted interactive, you should probably better run the job in the Syncovery GUI ... so I am not sure what your exact requirement is.
-
- Posts: 12
- Joined: Tue Jul 14, 2020 5:40 pm
Re: Commandline usage
Ideally, I would like to do the following, purely from the command line and without the application gui....
Preview the sync operation with potential changes to the command line and have the application stop.
Then, once the user has verified that the changes to be made are accepatble (by scrolling through the command line output, they will re run the operation as a sync.
The reason for this is that we do not wish to run the application gui....our source and destination folders are continuously changing and we are using a vb.net application to present a UI to the user, allowing them to select several options, including inclusion and exclusion of file that change based upon the source selected.
For our users, your UI is far too complicated....all they need is to see a list of files and their paths (not a tree view), so we can parse the command line after running your command line app as a separate thread/process and grab the STDOUT/STDERR.
So, an example of what we're trying to do (pseudocode here) would be:
YourApp.exe -myprofile arguments -PreviewChange
RETURNS:
-----Preview------
Changed File1
Changed File2
Changed File3
***At this point the user examine the output.....then
YourApp.exe -MyProfile -arguments -ActuallySyncChanges
RETURNS:
-----ActuallySyncChanges------
Changed File1
Changed File2
Changed File3
Hence, our need to to a "preview" to the command line, allow the user to read it, then re-run the operation as a sync if they have no objections.
Preview the sync operation with potential changes to the command line and have the application stop.
Then, once the user has verified that the changes to be made are accepatble (by scrolling through the command line output, they will re run the operation as a sync.
The reason for this is that we do not wish to run the application gui....our source and destination folders are continuously changing and we are using a vb.net application to present a UI to the user, allowing them to select several options, including inclusion and exclusion of file that change based upon the source selected.
For our users, your UI is far too complicated....all they need is to see a list of files and their paths (not a tree view), so we can parse the command line after running your command line app as a separate thread/process and grab the STDOUT/STDERR.
So, an example of what we're trying to do (pseudocode here) would be:
YourApp.exe -myprofile arguments -PreviewChange
RETURNS:
-----Preview------
Changed File1
Changed File2
Changed File3
***At this point the user examine the output.....then
YourApp.exe -MyProfile -arguments -ActuallySyncChanges
RETURNS:
-----ActuallySyncChanges------
Changed File1
Changed File2
Changed File3
Hence, our need to to a "preview" to the command line, allow the user to read it, then re-run the operation as a sync if they have no objections.
Re: Commandline usage
Hello,
yes this can be achieved with /RUNI, please try it.
yes this can be achieved with /RUNI, please try it.
Re: Commandline usage
Hello,
actually using /RUNI might be a bit tricky to control from your application, because you need to simulate screenshots in the right moment.
I will implement a switch like /PREVIEWLIST for you in the next update.
actually using /RUNI might be a bit tricky to control from your application, because you need to simulate screenshots in the right moment.
I will implement a switch like /PREVIEWLIST for you in the next update.
-
- Posts: 12
- Joined: Tue Jul 14, 2020 5:40 pm
Re: Commandline usage
Thank you for looking into it.
Would you please reply to this thread or email me directly once that has been completed?
Would you please reply to this thread or email me directly once that has been completed?