Yea diskpart is its own little beast.
Surprisingly really functional though. Probably my favorite windows command
Yea diskpart is its own little beast.
Surprisingly really functional though. Probably my favorite windows command
What are bottles?
Office 365 online can be a good stopgap for those cases if you need it.
TOZO NC9s. They’re cheap, decent ANC, and no app.
You csn hate a company and like a product. They aren’t mutually exclusive.
The crontab that is found at /etc/crontab very specifically states that it has a user field. I will readily admit that I might be misunderstanding it, but that feels pretty explicit to me.
Yes, you should never use sudo inside a users crontab. If you want to run as root then use the system crontab.
I appreciate the advice! I had never really heard about the distinction between the system crontab and user crontabs. While it makes sense in retrospect, I am entirely self-taught about this stuff, and nowhere I had looked had ever mentioned that there were two separate crontabs.
I would also encourage looking at systemd timers
Do you happen to know of a good resource to learn about those off the top of your head? I appreciate the suggestion!
I have edited /etc/crontab with the following 0 * * * * * root /mnt/nas/freshrss/backups/backup.sh. After waiting for the crontab to fire off, nothing happened.
I have edited /etc/crontab
with the following 0 * * * * * root /mnt/nas/freshrss/backups/backup.sh
. After waiting for the crontab to fire off, nothing happened.
So, right now I’m trying the system crontab instead of my user crontab.
Just to reiterate from my post, however, I have tried the full path. I was giving example paths. I should have been more explicit that by just “using dot” I meant using relative and absolute paths.
All paths have been full paths from the get go, though I did try cd-ing into the folder and running it with a relative path. My hope at this point is that it’s somehow a permissions issue as my storage setup is a bit odd with TrueNAS Scale running as a VM on ProxMox. Permissions with docker are usually hell, and I have to run literally everything that touches my NAS as root to get the permissions to play nicely, so it would make sense here that it’s just the permissions being upset and preventing access to the files.
I set a backup to run on the hour, so I’ll report back with whatever happens.
Yea just to further add:
Plastic is not an adhesive.