Open MurzNN opened 4 years ago
Also will be good to customize backup_base_directory
location, how it hardcoded as:
backup_base_directory="${backup_destination_path}/${HOSTNAME}/${script_config_name}"
but for regular users ${HOSTNAME}/${script_config_name}
are not needed.
I searching backup script that can be downloaded and run in user space (as regular user in home folder on any Linux system). Seems
glsysbackup
is good solution with option:root_privileges_required="0"
But the problem is that
script_base_path
,lock
andlog
folders are hard-coded:script_base_path="/usr/local/${script_name}" script_bin_directory="${script_base_path}/bin" script_lock_directory="${script_base_path}/var/lock" script_log_directory="${script_base_path}/var/log"
Can you please make them configurable via config file? Also can you please describe, which other potential problems can be happens when using your script in user space?
I am not sure, if i understood you correctly. What do you need that for? A possible solution could be to:
/usr/local/glsysbackup/bin/glsysbackup
./glsysbackup -c user.conf
An advantige of this solution is, that you have only one version of the original glsysbackup
script. Each user has its own config file.
Also will be good to customize
backup_base_directory
location, how it hardcoded as:backup_base_directory="${backup_destination_path}/${HOSTNAME}/${script_config_name}"
but for regular users
${HOSTNAME}/${script_config_name}
are not needed.
I have to think about it and let you know as far as i know how to deal with that.
I searching backup script that can be downloaded and run in user space (as regular user in home folder on any Linux system). Seems
glsysbackup
is good solution with option:But the problem is that
script_base_path
,lock
andlog
folders are hard-coded:Can you please make them configurable via config file? Also can you please describe, which other potential problems can be happens when using your script in user space?