Re: Strange system behavior

[buhrow%lothlorien.nfbcal.org@localhost (Brian Buhrow)]

        Hello.  I wonder if you can get a file of md5 checksums on all the
files in your build tree and then write a script to repeatedly check those
checksums.  This might give you a clue as to the nature of the problem.
For example, if you copy the build tree to another machine, get the
checksums, and then run the checksum test against the copy on the faulty
machine.  Running that for a day or two might yield interesting results.
-Brian

On Sep 21,  5:49pm, Paul Goyette wrote:
} Subject: Re: Strange system behavior
} On Wed, 22 Sep 2010, Eduardo Horvath wrote:
} 
} > On Tue, 21 Sep 2010, Paul Goyette wrote:
} >
} >> Someone suggested that maybe there was a corrupt library somewhere, so I
} >> mounted my build directory (via nfs) and did a 'build.sh install=/' but 
that
} >> didn't help, either.
} >
} > Oh, you're compiling over NFS?  Can you try doing everything locally
} > instead?
} 
} No, no!  :)  Not building via NFS.
} 
} The machine in question is a dedicated test-bed with its own local build 
} environment.
} 
} My "production build" environment is separate, on another machine, and 
} the builds there are also done on local disks.  I only use nfs to access 
} the install sets.
} 
} 
} -------------------------------------------------------------------------
} | Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
} | Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
} | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
} | Kernel Developer |                          | pgoyette at netbsd.org  |
} -------------------------------------------------------------------------
>-- End of excerpt from Paul Goyette