|
From: | Richard Frith-Macdonald |
Subject: | Re: What's up with gdomap??? |
Date: | Fri, 10 Feb 2006 11:08:31 +0000 |
On 10 Feb 2006, at 10:47, Chris B. Vetter wrote:
On 2/10/06, Richard Frith-Macdonald <richard@brainstorm.co.uk> wrote:On 10 Feb 2006, at 10:02, Chris B. Vetter wrote: It's certainly weird ... no way should it be using any significant amount of cpu.I recently trashed the GNUstep system startup script and did a very quick re-write. Apparently I forgot to add '-p' for not probing as option. Adding it and re-running the script 'fixed' the problem. That is, gdomap is now down to 0% My bad... Then again, why IS it using 95% when -p is specified?
That's a good question ... it shouldn't happen, and it's almost certainly to do with something odd about your network config.
What sort of output do you get if you do gdomap -f -d -d -d to get really verbose debug listing all probes sent and received?
[Prev in Thread] | Current Thread | [Next in Thread] |