John Doherty
jdoherty@gstype.com
Thu Jun 2 17:57:58 UTC 2005
On 6/2/05 at 11:47 AM, vjs@calcite.rhyolite.com wrote: >> Also, and oddly, the whiteclnt.dccw file winds up with a >> bogus date of 12/31/1969. > Such a timestamp of 0 on the whiteclnt.dccw hash table indicates > that the ASCII /var/dcc/whiteclnt file could not be parsed. Dccm, > dccifd, or dccproc (if you used them) should be whining in the > system log about syntax errors or host namesfile that cannot be > resolved in the whiteclnt. Very good. I'll look into that and expect that it will solve the problem. (Should have thought to look myself.) >> The last oddity that I notice is that there are two dccm processes >> running, and I don't recall that it used to be that way (although >> that may be just me misremembering). > That looks like the extra process present since 1.3.0 that restarts > dccm after obvious crashes. I had forgotten about that. Well, that makes sense, then. Thanks a lot, Vernon. -- John
More information about the DCC
mailing list