Closed JamesSaxon closed 3 years ago
This is still not working for me on reboot. This would also help with #19
ubuntu@pi:~$ sudo cp /etc/cron.d/cron-nm-exp-active-netrics blah
ubuntu@pi:~$ sudo reboot now
Connection to 192.168.1.5 closed by remote host.
Connection to 192.168.1.5 closed.
~ ssh pi
[...]
ubuntu@pi:~$ cat /etc/cron.d/cron-nm-exp-active-netrics
*/5 * * * * netrics env USER=$LOGNAME /usr/local/bin/netrics -p -n -d -t -b -u >>/tmp/nm/nm-exp-active-netrics/log/log.txt 2>&1
32 * * * * netrics env USER=$LOGNAME /usr/local/bin/netrics -s -l -u >>/tmp/nm/nm-exp-active-netrics/log/log.txt 2>&1
22 * * * * netrics env USER=$LOGNAME /usr/local/bin/netrics -i -u >/tmp/nm/nm-exp-active-netrics/log/log.txt 2>&1
ubuntu@pi:~$ cat blah
*/5 * * * * netrics env USER=$LOGNAME /usr/local/bin/netrics -p -n -d -t -b -u >>/tmp/nm/nm-exp-active-netrics/log/log.txt 2>&1
32 */2 * * * netrics env USER=$LOGNAME /usr/local/bin/netrics -s -l -u >>/tmp/nm/nm-exp-active-netrics/log/log.txt 2>&1
22 */6 * * * netrics env USER=$LOGNAME /usr/local/bin/netrics -i -u >/tmp/nm/nm-exp-active-netrics/log/log.txt 2>&1
* * * * * netrics env USER=$LOGNAME /usr/local/bin/netrics --tshark -u >/tmp/nm/nm-exp-active-netrics/log/log.txt 2>&1
this should be fixed with #20
Yes, this is working now for me. Thanks
On machine reboot, the crontab
/etc/cron.d/cron-nm-exp-active-netrics
reverts to a default one, instead of either the user's default or (I would prefer) whatever was edited & installed.