Stephan,
That did it! Thanks.
On Sun, Sep 29, 2013 at 12:22 PM, Krister Johnson wrote:
> Thanks will try tomorrow
>
> Krister Johnson
>
> On Sep 29, 2013, at 7:43 AM, Stephan Beal wrote:
>
> On Sat, Sep 28, 2013 at 10:57 AM, Stephan Beal wrote:
>
>> This one works for me:
>>
>> http://www.wand
Thanks will try tomorrow
Krister Johnson
> On Sep 29, 2013, at 7:43 AM, Stephan Beal wrote:
>
>> On Sat, Sep 28, 2013 at 10:57 AM, Stephan Beal wrote:
>> This one works for me:
>>
>> http://www.wanderinghorse.net/tmp/fsl-main.c
>
> Hi, Krister,
>
> i've been using that one since yesterday
On Sat, Sep 28, 2013 at 10:57 AM, Stephan Beal wrote:
> This one works for me:
>
> http://www.wanderinghorse.net/tmp/fsl-main.c
>
Hi, Krister,
i've been using that one since yesterday and have gone ahead and trunked it
(works for me!). Please try it out at your earliest convenience.
http://www.
On Thu, Sep 26, 2013 at 8:13 PM, Stephan Beal wrote:
> Not Found szFile=-1 zRepo=/libfossil.fsl/.fossil
>
> that "should" be zRepo=/libfossil.fsl. szFile<0 is a sign that it cannot
> be stat()'d (which makes sense, since the filename is wrong). i'm not yet
> sure why this happens only in the ch
On Thu, Sep 26, 2013 at 10:38 AM, Stephan Beal wrote:
> Just FYI: i can reproduce both the warning and the "not found" here using
> your setup. i'm at work now but can look at it more closely this evening.
>
i've narrowed down the "not found" problem - it's caused by confusion
caused by re-mappin
On Wed, Sep 25, 2013 at 10:04 PM, Krister Johnson wrote:
> 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 so
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 2
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, Not Found is the only thing there).
When I commen
On Wed, Sep 25, 2013 at 8:49 PM, Ron Wilson 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 UID==0 (root user).
On Wed, Sep 25, 2013 at 12:30 PM, Stephan Beal wrote:
> On Tue, Sep 24, 2013 at 9:36 PM, Richard Hipp 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
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 P
On Wed, Sep 25, 2013 at 7:03 PM, Krister Johnson 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
> using the IP a
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 W
On Wed, Sep 25, 2013 at 6:34 PM, Richard Hipp 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 true the
On Wed, Sep 25, 2013 at 12:30 PM, Stephan Beal wrote:
> On Tue, Sep 24, 2013 at 9:36 PM, Richard Hipp 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
On Tue, Sep 24, 2013 at 9:36 PM, Richard Hipp 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
> after entering t
On Tue, Sep 24, 2013 at 9:36 PM, Richard Hipp wrote:
> On Tue, Sep 24, 2013 at 12:43 PM, Krister Johnson wrote:
>
>> 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. I found this error elsew
On Tue, Sep 24, 2013 at 9:36 PM, Richard Hipp wrote:
> Circumstances make it difficult for me to work on this problem this week.
> But I'll look into it next week, if nobody else (read: "Stephan") fixes it
> first.
>
So no pressure ;). Tomorrow night i'll have my "work laptop" and will take
a lo
On Tue, Sep 24, 2013 at 12:43 PM, Krister Johnson wrote:
> 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. I found this error elsewhere in the mailing list, but the suggestions
> there did not
Unfortunately no... I also tried init'ing a new repo in the same location
(/etc/fossil/) and starting fossil with that repo...I get the same warning.
On Tue, Sep 24, 2013 at 12:17 PM, Stephan Beal wrote:
> On Tue, Sep 24, 2013 at 6:43 PM, Krister Johnson wrote:
>
>> I'm just getting started usin
On Tue, Sep 24, 2013 at 6:43 PM, Krister Johnson wrote:
> 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. I ...
> Why am I getting this warning? Thanks guys.
>
Is there a symlink involved? I
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.
I found this error elsewhere in the mailing list, but the suggestions there
did not apply (not on NFS). The fossil executable is located at /bin and
22 matches
Mail list logo
