Hello Proxmox,
On PBS (3.4), I had two things configured & working:
1. root@pam user was disabled (within /etc/proxmox-backup/user.cfg).
2. a cronjob was setup to initiate a prune, gc and sync with (@reboot /usr/bin/sleep 30; /usr/sbin/proxmox-backup-manager prune-job s-f932e83e-a384
This was done for two reasons:
1. I cannot have the root account accessible.
2. this PBS was my offline PBS system. Every once in a while all I would need to do is turn it on through its IPMI and it would automatically start a prune/sync/verify/GC.
When I updated to PBS 4, the cronjob stopped working when the root user was disabled. I tried adding the cronjob under a sudo user with (crontab -u PBS_admin -e) but the Proxmox-backup-manager command requests the root@pam credential.
Any way to re-enable my @boot sync/GC/prune cronjob without leaving root@pam enabled?
Thanks, Malcolm
On PBS (3.4), I had two things configured & working:
1. root@pam user was disabled (within /etc/proxmox-backup/user.cfg).
2. a cronjob was setup to initiate a prune, gc and sync with (@reboot /usr/bin/sleep 30; /usr/sbin/proxmox-backup-manager prune-job s-f932e83e-a384
This was done for two reasons:
1. I cannot have the root account accessible.
2. this PBS was my offline PBS system. Every once in a while all I would need to do is turn it on through its IPMI and it would automatically start a prune/sync/verify/GC.
When I updated to PBS 4, the cronjob stopped working when the root user was disabled. I tried adding the cronjob under a sudo user with (crontab -u PBS_admin -e) but the Proxmox-backup-manager command requests the root@pam credential.
Any way to re-enable my @boot sync/GC/prune cronjob without leaving root@pam enabled?
Thanks, Malcolm