Thanks.
Olivier
Are you running the commands above as root? If so, Fossil will
automatically put itself in a chroot jail on the directory containing
the repository and drop root privileges before doing anything else.
This is a security feature.
If you are going into a chroot jail, probably /dev/null and
/dev/urandom are no longer in that chroot jail. You can fix that by
running:
mkdir dev
mknod dev/null c 1 3
mknod dev/urandom c 1 9
See also the "managing server load" heading of
http://fossil-scm.org/fossil/doc/trunk/www/server.wiki where it talks
about the importance of making /proc available inside the chroot jail
so that Fossil can determine the load average.
Or, you can use the --nojail option on the "fossil server" command, in
which case Fossil will still drop its root privilege but will not
attempt to form a chroot jail. This is less secure, but probably
still plenty safe.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
