Dale,
Thanks for the feedback. I did find an article on Apples TIL stating that
the debuggerlock message is a harmless bug in the ethernet driver. No harm
other than filling the log.
I am curious what others are seeing for their load values when running
uptime
in the terminal. Brice sent me his values which were similar. My ISP
engineer tells me that they should all be below 1.0 (1.0 being 100% of
capacity) Here's my values.
>> [server:~] user% uptime
>> 1:43PM up 4:27, 1 user, load averages: 4.61, 3.80, 3.54
>> [server:~] user % uptime
>> 1:44PM up 4:28, 1 user, load averages: 2.54, 3.36, 3.38
>> [server:~] user % uptime
>> 1:44PM up 4:28, 1 user, load averages: 3.33, 3.42, 3.41
>> [server:~] user % uptime
>> 1:44PM up 4:28, 1 user, load averages: 3.14, 3.40, 3.39
>> [server:~] user % uptime
>> 1:44PM up 4:28, 1 user, load averages: 3.11, 3.29, 3.34
>> [server:~] user % uptime
>> 1:44PM up 4:28, 1 user, load averages: 3.12, 3.31, 3.34
>> [server:~] user % uptime
>> 1:44PM up 4:28, 1 user, load averages: 4.70, 3.75, 3.57
>> [server:~] user % uptime
>> 1:48PM up 4:32, 1 user, load averages: 2.54, 3.35, 3.42
>> [server:~] user % uptime
>> 1:48PM up 4:32, 1 user, load averages: 2.66, 3.31, 3.40
>> [server:~] user % uptime
>> 1:48PM up 4:32, 1 user, load averages: 2.55, 3.21, 3.34
TIA,
ken
> From: Dale LaFountain <dalel@xxxxxxxxxxxxx>
> Hi Ken,
> I have seen these message since I first installed OSXS 1.2, except my
> repeat messages are in the thousands... I asked multiple times on
> this and other lists, and didn't hear about any patches or fixes.
>
> The easiest way to get rid of the messages, and subsequent load
> creating by this logging is to kill/disable syslogd. Not the best
> solution if you need to see other logged activity, but it works.
>
> Or upgrade to OSX 10 client. I haven't seen these errors on 10
> client or server 2.0.
---
Tenon Intersystems' itools Mailing List
To unsubscribe: send mailto://itools-request@xxxxxxxxxxxxxxx
with the body: unsubscribe
|
