On 2/20/2013 07:52, Richard Hipp wrote:
So I just tried it.  I type:

    sudo /home/drh/bin/fossil server

and it is working fine for me.  Browsing to
"http://localhost:8080/test_env"; confirms that fossil has entered a
chroot jail prior to serving content.

I, too, can get fossil server to run as root when I make it serve a directory of *.fossil files.

My problem case is different. It fails when serving a single repository, either when given a *.fossil file name as ?REPOSITORY? or when run from within an open Fossil checkout:

    $ fossil serve /path/to/repo.fossil

Sorry for not specifying that in the original email. I had no reason to believe the two command forms would behave so differently with regard to permission handling.
fossil-users mailing list

Reply via email to