In article <4f08c38a$0$1705$742ec2ed@news.sonic.net>,
Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> In article <1kdhqp3.wqcxfitcf2h4N%pfjames2000@googlemail.com>,
> pfjames2000@googlemail.com (Peter James) wrote:
>
> > Firstly may I say that my broadband supply has a problem, which means
> > that when playing WoW I often find that I have lost contact with the
> > server. When after a few seconds the line is restored my character in
> > the game will not interact with the game and I need to log out and back
> > in again.
> >
> > Unfortunately when this happens the game hangs and I can't log out, I
> > can't exit the game, and I'm forced to switch off at the mains, re -boot
> > and then re-load the game.
> >
> > My options do seem limited. Force quit won't work whilst running WoW,
> > command+alt+esc won't work and neither does control+alt+delate, the old
> > Windows escape which I tried, just in case.
> > My broadband supplier is trying to get the line sorted, but until and
> > when I would welcome a solution.
> >
> > Using a 24" iMac 3.33 GHz Intel Core 2 Duo with OS 10.6.8
> >
> > It is a complete irritant, and I'm hoping someone here will be able to
> > help me.
> > Thanks,
> >
> > Peter
>
> Some of the Core 2 Duo Macs (especially the original Mini Server) have
> incorrect kernel settings that have never been addressed except for a
> few obscure Knowledge Base articles on Apple's support site. Run this
> in Terminal after you experience a hang (leaving the modem OFF may speed
> recovery):
>
> netstat -m
>
> You'll see some statistics dumped. The values for 'requests for memory
> denied' and 'requests for memory delayed' should be zero. If they're
> not, it means the kernel ran out of critical communications buffers.
> The trigger is typically network streams on a fast connection that
> aren't closed cleanly. The result is that networking fails and
> applications begin hanging; not even Force-Quit will work.
>
> To fix it, run this in Terminal:
>
> sudo nvram boot-args="ncl=262144"
>
> Reboot and try again. If you still see the problem, use:
>
> sudo nvram boot-args="ncl=524288"
>
> and reboot. This costs you some RAM so don't make the change unless
> 'netstat -m' shows the problem after a hang.
Interesting. As a Mac user, I never knew that, and it's good to know.
Mine came back with:
929/1770 mbufs in use:
851 mbufs allocated to data
78 mbufs allocated to socket names and addresses
841 mbufs allocated to caches
1085/1988 mbuf 2KB clusters in use
0/50 mbuf 4KB clusters in use
0/35 mbuf 16KB clusters in use
4744 KB allocated to network (37.5% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to drain routines
--
For all you know this message was...
Sent via an exclusive network, on a snobby portable computing device.