2007/3/4, roland Tollenaar <[EMAIL PROTECTED]>:
> May be adding a message queue and a non-RT task,
> the RT task sends messages through message queue
> and the non-RT task finally call syslog.
Sounds like a good idea. But first I must find out what is calling
syslogd in the first place and stop that happening.
You are right.
> Your RT task may be prepared to receive
> -ENOMEM if the queue if full.
Ah, this sounds like a lead. How would I confirm this and then how do
I change that setting?
I think I did not tell it right.
IF YOU set up a message queue between YOUR RT task and
YOUR non-RT task that call syslog then the RT task should
be prepared to full message queue.
I'm NOT telling that full message WOULD generate syslog call
I DON'T know.
> You may want to try alternatives syslog daemon
> implementation like syslog-ng (http://www.balabit.com/products/syslog_ng/)
> which exhibits far better performance than "standard" syslogd.
I'd much rather just switch it off entirely when I am running my
rt-task. If I have a problem and need to debug with it I can always
switch on.
For this then simply try
/etc/init.d/syslogd stop
During debugging I am not so worried about the hardness of
the RT behaviour.
Anyone know how to switch off syslogd or block all calls to it?
May be you can post the log excerpt you have in order
fo us to know where they come from?
log should show if they are coming from kernel or user process.
--
Erk
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
