there might be a common denominator here - this is happening on a Dell SC1435, dual-core Opteron 2212... maybe it's an AMD thing. That may change my plans for another server. ian j hart wrote: > On Tuesday 02 December 2008 14:40:19 Rick Chisholm wrote: > > Sorry I can't offer a solution but I can confirm this as an issue. > > I used to get this on our old work hardware; > CPU AMD athlon 2100+ (single core at 1733Mhz IIRC) PC3200 DDR. > > Since upgrading (Q6600 quad core at 2.4Ghz, DDR2 667Mhz?) I'm not getting this > any more. [Rubs lucky rubber chicken to avoid the kiss of death]. > > This suggests it may be a subtle timing issue which will be tricky to find. > > I got into the habit of running top after the reconfig. If one of the squid > owned processes hits 100% CPU, kill with extreme prejudice. Actually I still > do this. > > IIRC it was the old squid process which did this, but I could easily be wrong. > If you can confirm that it may help one of the developers to find the > problem. > > HTH > -- Rick Chisholm sysadmin Parallel42 e. rchisholm@xxxxxxxxxxxxx m. 519-325-8630 w. www.parallel42.ca
