gbonawitz
03-26-2007, 02:23 PM
I have two Tivos, and only one (let's say Tivo A) has a phone jack anywhere near it. On Tivo A I have tivocid & ncidd running for caller id to tv. On Tivo B I have tivocid running but have edited the config file to point to the ncidd on Tivo A.
I have edited rc.sysinit.author on both tivos to call the respective programs after the 2 AM startup. Here's my issue - I think Tivo B might be trying to run tivocid (looking for ncidd on tivo A) before ncidd on Tivo A has started. The caller id alway works fine on tivo A, but I notice the display doesn't come up on tivo B. When I telnet to tivo B and manually start tivocid, then it works.
I suppose I could put a sleep command on tivo B's rc.sysinit.author to wait before it tries to run tivocid, but I'm wondering if there's a slicker way to detect if ncidd is running on tivo a first before I try to run tivocid on tivo B. Reason being is sometimes I get lazy and echo new commands to rc.sysinit.author that I wouldn't want to bottleneck behind the sleep link for tivocid.
Of course, one option is to give up editing rc.sysinit.author via echo and use vi consistently..:)
I have edited rc.sysinit.author on both tivos to call the respective programs after the 2 AM startup. Here's my issue - I think Tivo B might be trying to run tivocid (looking for ncidd on tivo A) before ncidd on Tivo A has started. The caller id alway works fine on tivo A, but I notice the display doesn't come up on tivo B. When I telnet to tivo B and manually start tivocid, then it works.
I suppose I could put a sleep command on tivo B's rc.sysinit.author to wait before it tries to run tivocid, but I'm wondering if there's a slicker way to detect if ncidd is running on tivo a first before I try to run tivocid on tivo B. Reason being is sometimes I get lazy and echo new commands to rc.sysinit.author that I wouldn't want to bottleneck behind the sleep link for tivocid.
Of course, one option is to give up editing rc.sysinit.author via echo and use vi consistently..:)