Difference between revisions of "Restart CanIt"
From Roaring Penguin
| Line 11: | Line 11: | ||
This carries a slight risk of Bayes training being not working until the next Bayes run. However, the slight inaccuracy of Bayes data is highly unlikely to be noticeable in filtering performance. | This carries a slight risk of Bayes training being not working until the next Bayes run. However, the slight inaccuracy of Bayes data is highly unlikely to be noticeable in filtering performance. | ||
| − | Note: start-gracefully waits for any busy canitd tasks to finish, so in that sense it's a bit safer. | + | Note: start-gracefully waits for any busy canitd tasks to finish, so in that sense it's a bit safer. |
<div style="float:right; clear:both; margin-right:0.5em">[[Support Wiki | [Home]]]</div> | <div style="float:right; clear:both; margin-right:0.5em">[[Support Wiki | [Home]]]</div> | ||
[[category:All]][[category:Troubleshooting]] | [[category:All]][[category:Troubleshooting]] | ||
Revision as of 16:35, 2 November 2015
On occasion the CanIt process my stall or become hung. In these cases it may be necessary to restart CanIt to get it back to a fully functional state.
If this is the case and you feel it necessary to restart try the following from the command line as the root user:
/etc/init.d/canit-system restart-gracefully
However if the canitd process is truly hung, then restart-gracefully will be unresponsive. In this case terminate the command and use:
/etc/init.d/canit-system restart
This carries a slight risk of Bayes training being not working until the next Bayes run. However, the slight inaccuracy of Bayes data is highly unlikely to be noticeable in filtering performance.
Note: start-gracefully waits for any busy canitd tasks to finish, so in that sense it's a bit safer.
