Hi list,
I made 3 distinct packages, one per ibrdtn "module": ibrcommon, ibrdtn and ibrdtnd (all with 0.8 version).
Since I have a lot of available storage constraints (~8Mb), I disabled the support for: openssl,
802.15.4 (lowpan), sqlite, compression, tls, dtnsec and curl.
Those 3 BR packages seems to configure, compile and install as expected, and inside my embedded system, I have:
# ldd /usr/sbin/dtnd
librt.so.0 => /lib/librt.so.0 (0x401bb000)
libibrcommon-0.8.so.1 => /usr/lib/libibrcommon-0.8.so.1 (0x401c7000)
libibrdtn-0.8.so.1 => /usr/lib/libibrdtn-0.8.so.1 (0x40149000)
libm.so.0 => /lib/libm.so.0 (0x40199000)
libc.so.0 => /lib/libc.so.0 (0x400a6000)
libdl.so.0 => /lib/libdl.so.0 (0x4010d000)
libpthread.so.0 => /lib/libpthread.so.0 (0x4004a000)
ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x40097000)
#
# uname -a
Linux emb 2.6.38emb #68 Thu Feb 9 16:43:56 WET 2012 armv4tl GNU/Linux
#
# free -k
total used free shared buffers
Mem: 29296 20700 8596 0 188
-/+ buffers: 20512 8784
Swap: 0 0 0
#
# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 7.7M 6.1M 1.2M 84% /
tmpfs 14.3M 0 14.3M 0% /dev/shm
tmpfs 14.3M 56.0K 14.3M 0% /tmp
#
The problem is when I try to launch dtnd daemon with default configuration file I get:
# dtnd -c /etc/ibrdtnd.conf
Wed Jun 6 02:44:05 2012 INFO: Configuration: /etc/ibrdtnd.conf
Wed Jun 6 02:44:05 2012 INFO: IBR-DTN daemon 0.8.0 (build 52262)
Aborted
# echo $?
134
#
Also, system clock is correct.
If I change the daemon user to "daemon" I get more output, but the error remains
# dtnd -c /etc/ibrdtnd.conf --nodiscovery -d999999 --badclock --noapi -ieth0
Wed Jun 6 02:47:35 2012 INFO: Configuration: /etc/ibrdtnd.conf
Wed Jun 6 02:47:35 2012 INFO: IBR-DTN daemon 0.8.0 (build 52262)
Wed Jun 6 02:47:35 2012 INFO: debug level set to 999999
Wed Jun 6 02:47:35 2012 INFO: use logfile for output: /var/log/ibrdtn.log
Wed Jun 6 02:47:35 2012 INFO: Switching user to daemon
Aborted
# echo $?
134
#
I also tried with some modifications in config file without success.
Someone have idea what can cause these weird error?
Is the code 134 documented somewhere?
Thank you for your time,
João Ferreira