On Tue, Sep 24, 2013 at 9:36 PM, Richard Hipp d...@sqlite.org wrote:
On Tue, Sep 24, 2013 at 12:43 PM, Krister Johnson krist...@gmail.comwrote:
I'm just getting started using fossil. I currently get a SQLITE_WARNING:
file renamed while open: /etc/fossil/repo warning at the top of each
page.
On Tue, Sep 24, 2013 at 9:36 PM, Richard Hipp d...@sqlite.org wrote:
I think this is a bug. My theory is that Fossil is putting itself in a
chroot jail to handle each request, but it is doing so after opening the
database file. That's a huge no-no. The database file needs to be opened
On Wed, Sep 25, 2013 at 12:30 PM, Stephan Beal sgb...@googlemail.comwrote:
On Tue, Sep 24, 2013 at 9:36 PM, Richard Hipp d...@sqlite.org wrote:
I think this is a bug. My theory is that Fossil is putting itself in a
chroot jail to handle each request, but it is doing so after opening the
On Wed, Sep 25, 2013 at 6:34 PM, Richard Hipp d...@sqlite.org wrote:
Do you mean chroot()? If so, then I think the answer is yes. But I
don't think chdir() matters.
yes/no (or jein, as the Germans say) - file_chdir() does the chroot() if
the 2nd param is true, and enter_chroot_jail() passes
Dumb question - is there an easy way to grab source if fossil clone won't
work? I get an error that www.fossil-scm.org can't be resolved when i try
to clone the project to make the change you suggested. I tried cloning
using the IP address but get a 404 error. Is the source zipped somewhere?
On
On Wed, Sep 25, 2013 at 7:03 PM, Krister Johnson krist...@gmail.com wrote:
Dumb question - is there an easy way to grab source if fossil clone won't
work? I get an error that www.fossil-scm.org can't be resolved when i try
to clone the project to make the change you suggested. I tried cloning
It looks similar to this issue -
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg09338.html
nslookup resolves the address fine, but the fossil executable doesn't for
some reason. I will build from the zip with the suggested change and report
back
On Wed, Sep 25, 2013 at 12:10
On Wed, Sep 25, 2013 at 12:30 PM, Stephan Beal sgb...@googlemail.comwrote:
On Tue, Sep 24, 2013 at 9:36 PM, Richard Hipp d...@sqlite.org wrote:
I think this is a bug. My theory is that Fossil is putting itself in a
chroot jail to handle each request, but it is doing so after opening the
On Wed, Sep 25, 2013 at 8:49 PM, Ron Wilson ronw.m...@gmail.com wrote:
Why would the database be opened before doing the chroot?
i believe the reason is that because the bit which does the db-open does
not know that a chroot may (depending on the UID) be pending. The chroot
only happens when
It's bed time over here in CET, but i will take a closer look at it
tomorrow. The root of the problem is now known, i think, we just need to
find the right combination.
(sent from a mobile device - please excuse brevity, typos, and top-posting)
- stephan beal
http://wanderinghorse.net
On Sep
Stephan:
I changed main.c to look as follows. I wasn't sure which code block you
meant by first and second so I tried both instances. With the code as
shown, I get no sqlite_warning, but I also get a big Not Found message
(if I view page source, h1Not Found/h1 is the only thing there).
When I
Hello all,
I created a local repository under Fossil 1.24, checked in some files,
did some development, checked in some changes, and then copied the
repo to server which is running Fossil 1.27. When notified by the
server's fossil that the DB schema was out of date, I ran fossil
rebuild on the
12 matches
Mail list logo
