Hello, I just installed the script and I think that it is exactly what I need - :).
But 'I got a bit of trouble with the configuration file ezrsync.conf.
Maybe i'm wrong but I have seen that, in routine do_backup,
the script do not use / etc / ezrsync.d / ezrsync.conf but / etc / ezrsync.conf.d / * differently than described in the documentation.
I had to refresh my lack of knowledge of BASH :-) (and my English)
could you check if I'm right?
I also think that it would be useful, perhaps with a directive like: "dump_settings 0/1" to print the list of execution parameters.
I put the script in a production environment and uninstalled rsnapshot :-).
Thank you and I will try to be helpful.
bye, Luca
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The 'documentation' describes the intended and I think also the actual behaviour. Maybe the documentation isn't clear enough, but there quite a bit of options. If you only have /etc/ezrsync.conf that's fine. If there are additional scripts in /etc/ezrsync.conf.d/ they will be used as well. If you don't have /etc/ezrsync.conf or a --mainconf option, the files in /etc/ezrsync.conf.d/ will be used.
The default locations of these scripts can be changed, /etc/ezrsync.conf by using the commandline option --mainconf, and /etc/ezrsync.conf.d/ in the main configfile.
Finally, if you use the commandline option --soleconf, then that will be the only configfile used.
Are we on the same page now? If not, please let me know!
If --verbose is 2 or more, you will get a list of all the config options as read. Is that what you mean?
Cheers,
Peter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, we are on the same page.
I had a bit of confusion by putting the configuration file instead of / etc in / etc / exrsync.d, a sort of hybrid between the two possibilities and instead control exactly the path I thought "does not read the configuration file :-) '
In my opinion it would be better to make mandatory a configuration file, if not found, a message such as "/ etc / ezrsync.conf not found" unless overridden by the command line.
ok for the verbose
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It should read any configuration file in the configdir. A main configfile isn't mandatory, so I don't think there is need of a special message. In most log levels it reports about which configfiles are used, and also if it's a main configfile (or sole, or not).
You're welcome, glad to be of help. :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With version 0.52-beta of ezrsync out in the open, I'm open for comments, suggestions, feature requests and bug reports.
Hello, I just installed the script and I think that it is exactly what I need - :).
But 'I got a bit of trouble with the configuration file ezrsync.conf.
Maybe i'm wrong but I have seen that, in routine do_backup,
the script do not use / etc / ezrsync.d / ezrsync.conf but / etc / ezrsync.conf.d / * differently than described in the documentation.
I had to refresh my lack of knowledge of BASH :-) (and my English)
could you check if I'm right?
I also think that it would be useful, perhaps with a directive like: "dump_settings 0/1" to print the list of execution parameters.
I put the script in a production environment and uninstalled rsnapshot :-).
Thank you and I will try to be helpful.
bye, Luca
Hi Luca,
The 'documentation' describes the intended and I think also the actual behaviour. Maybe the documentation isn't clear enough, but there quite a bit of options. If you only have /etc/ezrsync.conf that's fine. If there are additional scripts in /etc/ezrsync.conf.d/ they will be used as well. If you don't have /etc/ezrsync.conf or a --mainconf option, the files in /etc/ezrsync.conf.d/ will be used.
The default locations of these scripts can be changed, /etc/ezrsync.conf by using the commandline option --mainconf, and /etc/ezrsync.conf.d/ in the main configfile.
Finally, if you use the commandline option --soleconf, then that will be the only configfile used.
Are we on the same page now? If not, please let me know!
If --verbose is 2 or more, you will get a list of all the config options as read. Is that what you mean?
Cheers,
Peter
Yes, we are on the same page.
I had a bit of confusion by putting the configuration file instead of / etc in / etc / exrsync.d, a sort of hybrid between the two possibilities and instead control exactly the path I thought "does not read the configuration file :-) '
In my opinion it would be better to make mandatory a configuration file, if not found, a message such as "/ etc / ezrsync.conf not found" unless overridden by the command line.
ok for the verbose
Bye. Luca ( and tank's a lot )
It should read any configuration file in the configdir. A main configfile isn't mandatory, so I don't think there is need of a special message. In most log levels it reports about which configfiles are used, and also if it's a main configfile (or sole, or not).
You're welcome, glad to be of help. :-)