Jul 25 07:12:03 unix syslog: gb7mbc<-:PC84^GB7MBC^GB7MBC-11^GB7MBC-16^sh/dx^~^M
Jul 25 07:12:03 unix syslog: gb7mbc->:PC84^GB7MBC^GB7MBC-11^GB7MBC-16^sh/dx^~^M
Jul 25 07:12:03 unix syslog: gb7mbc<-:PC84^GB7MBC^GB7MBC-11^GB7MBC-16^sh/dx^~^M
Jul 25 07:12:03 unix syslog: gb7mbc->:PC84^GB7MBC^GB7MBC-11^GB7MBC-16^sh/dx^~^M
Jul 25 07:12:03 unix syslog: gb7mbc<-:PC84^GB7MBC^GB7MBC-11^GB7MBC-16^sh/dx^~^M
If I try to do the same to pe0mar-11, through gb7mbc.. ie like this
gb7mbc-11 -> gb7mbc -> pe0mar-11
The same happens. During this time, syslogd takes approximately 60% of CPU
time. Can anybody confirm this? It does eventually stop after maybe 5
minutes.
Ian
--
Ian Maude G0VGS Morecambe Lancs UK | NTSnet : g0vgs@gb7mbb.#16.GBR.EU INTERnet: eenqwnw.rbupvohs@prw.net | AMPRnet: iacgoayd@coara.or.jp viwyga.iimtoc@didema.ru | WWW=http://www.lurpac.lancs.ac.uk/g0vgs/ Sysop of GB7MBC, the Morecambe Bay Cluster, running Linux and CLX