Hi there,
Thanx to:
Michael Crowley (mcrowley_at_mtholyoke.edu)
Ian Goodacre (Ian.Goodacre_at_MBS.GOV.ON.CA)
Donn Aiken (daiken_at_regents.edu)
Tom Webster (webster_at_ssd.lgb.cal.boeing.com)
Anthony Talltree(aad_at_nwnet.net)
responses fell into two camps : those who suggested ways to find out what was
using all the machine resources; and those who suggested what might be causing
the machine to go into an extended pause.
The latter group, suggesting DNS, YP and NFS were correct. It was DNS, via
incorrect configuration of named.boot. After lookup data was no longer
considered current, it was looking in the wrong place to reload, and timing out
before going back to local data.
Cheers,
Martin Gorman
TDUNIX, Commercial Union
Received on Mon Jun 22 1998 - 14:46:53 NZST