Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Straightening\s+out\s+my\s+log\s+after\s+a\s+network\s+problem\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Straightening\s+out\s+my\s+log\s+after\s+a\s+network\s+problem\.\s*$/: 2 ]

Total 2 documents matching your query.

1. [TRLog] Straightening out my log after a network problem. (score: 1): Author: rnygren@epix.net (Bob Nygren); Date: Mon, 10 Jun 2002 21:22:08 -0400; Hi, I ran TR this past weekend for the VHF contest. With a computer at each station, it was a four computer network. Computer "A" went down twice before dying completely. It was replaced after 500 or; /archives//html/TRLog/2002-06/msg00054.html (6,902 bytes)
2. [TRLog] Straightening out my log after a network problem. (score: 1): Author: geoiii@kkn.net (George Fremin III - K5TR); Date: Mon, 10 Jun 2002 18:44:14 -0700; Here is what I would do: Make copies of each computers log and save them to a safe place. Make sure you know what file came from what computer. In POST L there is a routine to pull computer ID out of; /archives//html/TRLog/2002-06/msg00056.html (8,302 bytes)

Current List: 1 - 2
Page: [1]