_filename_final='$_tdir/proxmox_backup_'$_HOSTNAME'_'$_now'.tar.gz' _filename7='$_tdir/proxmoxreport.$_now.txt' _filename6='$_tdir/proxmoxpackages.$_now.list' _filename5='$_tdir/proxmoxvbios.$_now.tar' _filename4='$_tdir/proxmoxcron.$_now.tar' _filename3='$_tdir/proxmoxroot.$_now.tar' # register the cleanup function to be called on the EXIT signal _tdir=$(mktemp -d $_tdir/proxmox-XXXXXXXX) # number of backups to keep before overriding the oldest one # example: export BACK_DIR='/mnt/pve/media/backup # default value can be overridden by setting environment variable before running prox_config_backup.sh # Contributors aboutte, xmirakulix, bootsie123 Is there a way to remove the need to press enter from the script? My guess is because of the requirement to press enter to make it run once the script is started. When I add it to the crontab (crontab -e), it does not seem to run. I can run the script manually (./prox_config_backup.sh) and it completes the backup, but it requires pressing enter to run. I found a script that backs up all of my PVE host config data to a NFS share on my NAS.

Fbackup edit crontab