site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com I agree. But I'm not using stdio. I shouldn't have said "stdin"... http://lists.apple.com/archives/Unix-porting/2006/Jan/msg00072.html http://lists.apple.com/archives/Unix-porting/2006/Jan/msg00084.html -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... On Sep 6, 2008, at 1:37 PM, Nicolas Roussel wrote: In general, you should avoid multiple layers of buffering. I would suggest turning buffering off at the stdio layer using setbuf(3). I'm simply passing 0 as the file descriptor parameter to CFFileDescriptorCreate. And I'm not using any Carbon or Coca stuff for the moment (check the code in my first message). It seems others have had problems try to detect user input on the terminal with kqueue: Could this be related to my problem with the CFFileDescriptor? Try fstating fd 0 and looking at the S_IFMT bits in the st_mode field and see what flags are set in it. If it's a character or block special device, look at the major and minor fields of the st_dev and match them to a device in /dev. This email sent to site_archiver@lists.apple.com