All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Daniel Adams <dadams81@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Problem using sem_open and rt_sem_create
Date: Thu, 29 Jan 2009 07:38:11 +0100	[thread overview]
Message-ID: <49814ED3.9080607@domain.hid> (raw)
In-Reply-To: <ba9b368a0901282227i705ebe80oe75782ccc5cdc17f@domain.hid>

Daniel Adams wrote:
> Hi *,
> 
> I'm fairly new to Xenomai and am having a few issues and was wondering if
> anyone could provide me with help
> 
> I have written some code to create a process which waits on a named
> semaphore and then there is another process which posts to it. I originally
> developed the code using the posix interface under a standard Linux
> environment and have proved it works.
> I have since ported the code so that the waiting half creates and waits on
> the semaphore using the native skin and the posting half uses the posix
> skin.
> 
> I tried naming the semaphore using the leading '/' as the posix standard
> suggests, but found that using the '/' causes the rt_sem_create(&rt_sem,
> SEM_NAME, 0, S_PULSE)  to return EINVAL. Removing the '/' allows the
> semaphore to be created but now when I try to open the semaphore
> with sem_open(SEM_NAME, O_EXCL), I get an error that the file doesn't exist.
> Is there something that I'm missing? I've check the registry and the
> semaphore appears under /proc/xenomai/registry/native/semaphores/.

The objects created by the two skins are completely separate.

-- 
					    Gilles.


  reply	other threads:[~2009-01-29  6:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  6:27 [Xenomai-help] Problem using sem_open and rt_sem_create Daniel Adams
2009-01-29  6:38 ` Gilles Chanteperdrix [this message]
2009-01-29  6:46   ` Daniel Adams
2009-01-29  7:13     ` Gilles Chanteperdrix

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=49814ED3.9080607@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=dadams81@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.