-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't run a printf command #2
Comments
So this one makes sense -- just like My assumption had been that if a user wanted that, they'd configure grapple with something along the lines of I could look into a config option to turn on Popen's |
All good. I'll have to find a different solution. |
You could put that/those lines into a shell script, with a shebang at the top, or yeah, wrap it in a |
That's were I started, a shell script with a shebang!
|
Well, I've now implemented the https://github.com/lingfish/proxmox-grapple/releases/tag/1.5.5 |
I will give it a go. I got autorestic working in the standard shell script by including PATH=$PATH before calling autorestic (don't ask me why it works)
|
Not sure what is happening but when I run the following it errors.
But works from command line:
root@pve01:~# printf "$(date) PVE hook script start pve01 - $(pveversion)\n" | tee /mnt/ext_usb_01/pve01.log
Error in the Proxmox backup console:
The text was updated successfully, but these errors were encountered: