This looks to me like a portability issue -- fslibtest works fine for me on GNU/Linux (and you're reporting for a BSD system). I've filed this on Mantis under https://gnunet.org/mantis/view.php?id=976
Since I don't have access to a BSD box and since it seems that our BSD maintainer has abandoned the port, I don't see much that I can do to help you based on this data at this point -- other than saying that the testcase should succeed ;-). One thing that may help the diagnosis is running gnunetd with a higher log-level and/or including the LOG output from gnunetd in the output (just edit check.conf in the fs/lib/ directory) -- typically gnunetd should then log some indication as to what was going wrong in fslibtest (to /tmp/gnunet-check-fslib/logs). With that info, we maybe able to figure out what is going on. Christian _______________________________________________ Bug-GNUnet mailing list Bug-GNUnet@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnunet
