From: Roland Tollenaar <rwatollenaar@domain.hid>
To: Eric Noulard <eric.noulard@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] syslogd breaking rt behaviour of xenomai?
Date: Mon, 05 Mar 2007 07:59:14 +0100 [thread overview]
Message-ID: <45EBBFC2.7080101@domain.hid> (raw)
In-Reply-To: <cbe23c50703041007i743c2babjdf914d3b2b3ced91@domain.hid>
Hi
> 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
I'll try this later to see whether it improves matters.
>
>> 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.
Off the top of my head (am not at the linux box right now)
xeno-(something): buffer overflow bla bla (fd=[number]), message discarded
The [numer has been anything between 0 and 5. I presume the useful part
is the xeno-(something) where the something will tell us what is making
the calls?
I will not be able to run the system today so I post this memory version
so long. :)
Regards,
Roland.
>
>
>
prev parent reply other threads:[~2007-03-05 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 16:18 [Xenomai-help] syslogd breaking rt behaviour of xenomai? roland Tollenaar
2007-03-04 16:45 ` Eric Noulard
2007-03-04 17:52 ` roland Tollenaar
2007-03-04 18:05 ` Sebastian Smolorz
2007-03-04 18:07 ` Eric Noulard
2007-03-05 6:59 ` Roland Tollenaar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45EBBFC2.7080101@domain.hid \
--to=rwatollenaar@domain.hid \
--cc=eric.noulard@domain.hid \
--cc=rolandtollenaar@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.