Advertisements Ive tried to keep one of our favorite tweaks from inexplicably failing. Yes, I read and re-read the threads on this subject and did the suggested file changes to keep this problem from recurring. CallerID still quit working every couple of days. From my experience and from other posts on the subject, a reboot brings callerID back to life. I know you can also restart NCID from a bash prompt, but either option is an irritating process as youve already missed a least one call before you realize the server is stopped or hung. I also noted the cidcall log would go missing at some point and would not return even after a reboot. The only way I could get callerID to work correctly again with logging was to do a tweak uninstall and tweak install. I decided that if a reboot every Sunday and Wednesday was a good thing to do, then doing a reboot every day couldnt hurt. So, I modified the crontabs root file to force a reboot every day based on my time zone. I would think it a matter of good practice that the crontab date and time should reflect your time zone and match the system time that your callerID box is using. So I modified all other crontab tasks to reflect the correct time zone as well. On my callerID DTiVo, those tasks include stopping and starting TWP, daily fakecall, cron.test.out deletion, log wiping, and season pass backup. Since forcing a daily reboot two weeks ago with a match to my system time zone, NCID has not stopped unexpectedly and the cidcall log has not gone away. Tivocid clients are displaying fine as well. YMMV but this seems to have done the trick for keeping callerID up and running for my setup.