All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "M. Koehrer" <mathias_koehrer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] removing orphaned xenomai registry entries
Date: Mon, 20 Nov 2006 14:27:52 +0100	[thread overview]
Message-ID: <1164029272.5006.95.camel@domain.hid> (raw)
In-Reply-To: <5517606.1164028545775.JavaMail.ngmail@domain.hid>

On Mon, 2006-11-20 at 14:15 +0100, M. Koehrer wrote:
> Hi everybody,
> 
> especially in the development phase of a project, I have the situation to create some 
> entries like events that end up in the Xenomai's registry.
> However, while developing I exit my application before processing the clean up phase.
> This means, that I have a couple of orphaned events in the registry
> (e.g. in /proc/xenomai/registry/native/events).
> How can I force Xenomai to remove this entries?
> Is there something like a rmxeno  that works like rm or rmmod and removes specified
> elements? (if not: Isn't this an idea for any of the next versions of Xenomai....)
> The only way I found out is to reboot the PC which is not nice as it takes a while.
> Of course, in a final application I should never have this situation, however in the development
> phase this might occur fairly often.
> 
> Thanks for any feedback on this.

Yould could create a small application finding existing nodes
under /proc/xenomai/registry/native, bind to them depending on their
type (e.g. rt_event_bind(&desc, ...)), then call the proper deletion
routine against the bound descriptor (e.g. rt_event_delete(&desc)).

> 
> Regards
> 
> Mathias
> 
-- 
Philippe.




      reply	other threads:[~2006-11-20 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 13:15 [Xenomai-help] removing orphaned xenomai registry entries M. Koehrer
2006-11-20 13:27 ` Philippe Gerum [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=1164029272.5006.95.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=mathias_koehrer@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.