• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: pseudo-device pty >32
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pseudo-device pty >32


  • Subject: Re: pseudo-device pty >32
  • From: Terry Lambert <email@hidden>
  • Date: Mon, 6 Nov 2006 12:31:19 -0800

On Nov 5, 2006, at 11:07 PM, Tim Baur wrote:

On Sun, 5 Nov 2006, Terry Lambert wrote:
In other words, it's an administrative pilot error that's at fault, and not a problem with the implementation.

I'd find it pretty difficult to agree how it would be "pilot error" or incorrect settings since we're talking about default config shipped. not something that has been tweaked.

If you were running Mac OS X Server, as opposed to the desktop version of the OS, then in theory, those knobs should have been tweaked for you as part of the Mac OS X Server install. If this is the case, and they weren't, you need to file a bug report.


Otherwise, you can get around the default limits by doing the tweaking I suggested, but I'm not going to give a "cookbook" for this, since it would be inappropriate for iBooks with 128M of memory, and I know people would probably tweak things anyway, if they had a cookbook for it, and their machines would start to fall over under load, rather than simply load shedding.


having said that, understand those defaults may very well be reasonable and acceptable for the average user.

Correct. The average Macintosh user is not going to be able to tweak things the way a UNIX admin would tweak them, i.e. remove all constraints, load the system to failure, and then back the administrative limits down to just below the peak at which failure occurs to balance load capacity vs. failure point, and thus maximize their capacity.


Meanwhile, normal Mac users tend to have a really mixed general purpose computing load, unlike servers, which tend to be dedicated to a single function -- so it's nearly impossible to predictively arrive at what administrative limits are reasonable, if all you have is the hardware specs and no idea of the machine's intended role. About the best you can do is pick administrative limits that don't constrain 99% of the typical uses for the machine, but protect it from failing, and tell the remaining 1% that they need to do additional administrative tweaking for their out of the box use cases.

-- Terry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: pseudo-device pty >32
      • From: Tim Baur <email@hidden>
References: 
 >pseudo-device pty >32 (From: Tim Baur <email@hidden>)
 >Re: pseudo-device pty >32 (From: Terry Lambert <email@hidden>)
 >Re: pseudo-device pty >32 (From: Tim Baur <email@hidden>)
 >Re: pseudo-device pty >32 (From: Terry Lambert <email@hidden>)
 >Re: pseudo-device pty >32 (From: Tim Baur <email@hidden>)

  • Prev by Date: Re: XXXX is not compatible with its superclass, 13IOAudioEngine superclass changed?
  • Next by Date: Re: pseudo-device pty >32
  • Previous by thread: Re: pseudo-device pty >32
  • Next by thread: Re: pseudo-device pty >32
  • Index(es):
    • Date
    • Thread