Larry,
I believe it's expected behavior on Leopard, though you may want to
file a bug at least against the documentation. The following links
provide more information on this topic:
http://lapcatsoftware.com/blog/2008/01/06/logging-in-leopard/
http://boredzo.org/blog/archives/2008-01-19/next-week-apple-system-
logger
-Jeff
On Mar 9, 2008, at 11:08 PM, Larry Campbell wrote:
The NSLog(v) documentation says:
NSLogv writes the log to STDERR_FILENO if the file descriptor is
open. If that write attempt fails, the message is sent to the
syslog subsystem, if it exists on a platform, with the LOG_USER
facility (or default facility if LOG_USER does not exist), with
priorityLOG_ERR (or similar). If both of these attempts to write
the message fail, the message is discarded.
This is not true. Even though I've redirected STDERR_FILENO to my
own log file, using dup2, the messages still go into system.log.
(Yes, they are going into my log file, too.) This is very annoying
because it wastes disk space and makes syslogd spin, burning up CPU.
This is on Leopard; I don't remember if it also happened on Tiger.
Is this a known bug? Is there any way to stop it?
- lc
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
