From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <54F5C020.8090102@xenomai.org> Date: Tue, 03 Mar 2015 15:07:28 +0100 From: Philippe Gerum MIME-Version: 1.0 References: <54F58A4C.7030006@xenomai.org> <54F5BE3F.4010008@xenomai.org> In-Reply-To: <54F5BE3F.4010008@xenomai.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] Xenomai/cobalt: low_init(): binding failed: Function not implemented error issued when trting to run latency app on xeno 3.x-rc3 List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Helder Daniel , "Xenomai@xenomai.org" On 03/03/2015 02:59 PM, Philippe Gerum wrote: > On 03/03/2015 02:03 PM, Helder Daniel wrote: >> Hi Philippe, >> >> Thanks for your very quick response. >> I am installing cobalt in a physical pc for testing cobalt. >> >> Meanwhile I tried what you suggested to check the registry in Mercury: >> >>> If the registry could not be mounted, then you can't see it, that is >>> expected. >>> 1. Do you have /var/run on your system? >>> >> Yes I have (but no xenomai entry): >> >> ls /var/run >> >> acpid.pid exim4 NetworkManager.pid >> sm-notify.pid >> acpid.socket gdm3 pm-utils sshd >> atd.pid gdm3.pid rpcbind sshd.pid >> avahi-daemon initctl rpcbind.lock udev >> console initramfs rpcbind.pid udisks >> ConsoleKit lock rpcbind.sock utmp >> console-kit-daemon.pid motd.dynamic rpc.statd.pid vmblock-fuse >> crond.pid mount rsyslogd.pid vmtoolsd.pid >> crond.reboot mpt-statusd.pid sdp >> dbus mpt-statusd.status sendsigs.omit.d >> dhclient.eth0.pid network shm >> >>> 2. Does passing --registry-root=/tmp to the application fix the issue? >> >> No. Gives the same error: >> >> ./writeport --registry-root=/tmp >> 3"004.187| WARNING: [main] cannot connect to registry daemon >> 3"004.187| BUG: [main] initialization failed, EAGAIN > > Does your PATH variable include $prefix/sbin? > (typically /usr/xenomai/sbin unless you set a different installation > prefix when configuring). > > Bottom line is that the sysregd executable must be found when scanning > the PATH variable. > No actually, you don't need that if sysregd still appears in $prefix/sbin as built. Please send the output of "strace -f" on the latency executable. -- Philippe.