thanks for the reply, i removed the ~
question : i noticed dashwhale use a cron job as follows :
*/2 * * * * rootopt/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 ?
They're showing you the system crontab syntax frometc/crontab
I wouldn't recommend manually editing this file.
If you *need* to schedule a root crontab, just switch to root and add it to roots userland crontab
sudo su - ; crontab -e
But, in principle, I don't recommend running anything automatically as root that pulls updates.
And, no, clearing the debug log as root user is a one-size-fits-all approach to the problem.
It's better to perform maintenance as the user running the program.
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 haven't looked closely enough at the dashwhale code to have any advice, but a quick glance shows that it should be able to run from anywhere. /opt is just a standard place (in some distros/schools of thought) to place "other" stuff.
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.
Dashman doesn't do monitoring yet, only installs and updates.
Look for something comprehensive next year sometime, maybe early, maybe later. (Lots of other stuff to build first.)
But, fair warning, I don't know if I'm going to attempt supporting Windows.