You are correct if you are using a recient version of NCID. I assumed you were using an old version of the startncid script and then completely forgot about the newer version using pgrep. Here are the first few lines of the current version:
Originally Posted by Soapm
If you are using a current version of startncid, then make sure it starts ncidd. It could be killing it and not restarting it. Look at the end of the /var/log/ncidd.log to see if it was killed and not restarted or if it got into trouble when restarting.
# script to start NCID
# Requires the "pgrep" command
# Last modified by jlc: Mon Aug 30, 2010
The /var/hack/bin/initmodem shell script should be used as a cron job if you think the modem is a problem. It uses ncidd to reinitialize the modem. You can run it manually and then check ncidd.log to make sure it initialized the modem. It was last modified in 2010.
The problem I have is NCID will run a few days then a call will come and nothing shows on the screen. I can kill all the PID's and restart it and it will run a little while longer. I thought I could eliminate having to manually restart the app if I have it "refresh" itself each day.