Re: Anything I should know about thread safety and fprintf?
Re: Anything I should know about thread safety and fprintf?
- Subject: Re: Anything I should know about thread safety and fprintf?
- From: "Jonathan del Strother" <email@hidden>
- Date: Thu, 24 Jan 2008 11:16:46 +0000
On Jan 24, 2008 7:00 AM, Jordan K. Hubbard <email@hidden> wrote:
>
> On Jan 23, 2008, at 5:02 PM, Terry Lambert wrote:
>
> > The only real way to talk to the system logging facility is via
> > syslog()
>
> Which is how you should generate log messages only if you wish to use
> the deprecated, purely-for-backwards-compatibility interface. :-)
>
> Please use asl(3) for all new code. It's a far better, more flexible
> interface.
Ah. I thought the standard way of system logging was just
fprintf(stderr, ... ).
I still have no idea why I should be getting stuck in write() like
that, but I've switched to asl and the problem seems to have magically
disappeared...
Thanks for the help,
Jon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden