0 0 * * * > ~/full/path/to/.dash/debug.log
Above wouldn't work. It would expand to /home/user/home/user/.dash/debug.log
A full path already includes the portion that the ~ would expand to.
Generally, it's more compatible to be explicit than to rely on shell expansion of the $HOME environment variable using ~
thanks for the reply, i removed the ~
question : i noticed dashwhale use a cron job as follows :
*/2 * * * * root /opt/dashwhale-updater/dwupdater
why is root used in there ? and should root be used in the above mentioned cron job code to clear de debug.log ?
sidenote : i tried to get their Dashwhale remote monitoring part to work this morning, but i have dashd running from my home/user directory
and it just wouldn't monitor it correctly. Problem was that i seem to have no rights to move files in the "opt" folder through WINSCP, so i ended up trying
to adjust their code to home/user settings (which didnt work as i hoped). So now i'm just using their cron job code and files to restart my masternodes
if necessary and disabled remote monitoring for now.
I'm aware of your own monitoring software by the way Moocowmoo, but i was hoping to get something working in windows as i'm more comfortable in there.
If you some day could make your own monitoring software ready for windows use, that would be great.