Dmitry,
Here is how I have my fossil repository setup. The following
configuration is in /etc/xinetd.d/fossil-myproject
service fossil-myproject
{
flags= REUSE
socket_type= stream
wait= no
user= fossil
server
On Tue, Jan 25, 2011 at 10:20:06AM -0500, Bill Whiting wrote:
> Dmitry,
> I checked the permissions. I am not running this from apache, fossil is
> launched from xinetd, so the fossil process is owned by the same user
> that owns the fossil repository file.
I don't think this is generally true.
Richard,
That's it (sort of). The /var file system is full. I thought I had
verified that all of the file systems had some free space, but
overlooked /var. I extended the file system and the push succeeded.
Thanks!
//Bill
On 01/25/2011 10:19 AM, Richard Hipp wrote:
>
>
> On Tue, Jan 25, 201
On Tue, Jan 25, 2011 at 10:09 AM, Dmitry Chestnykh
wrote:
> > Error: Database error: unable to open database file
> > CREATE TEMP TABLE onremote(rid INTEGER PRIMARY KEY);
>
> Check permissions and ownership of fossil repository file. Are your web
> process allowed to write to this file?
>
Dmitry,
I checked the permissions. I am not running this from apache, fossil is
launched from xinetd, so the fossil process is owned by the same user
that owns the fossil repository file.
Thanks,
//Bill
On 01/25/2011 10:09 AM, Dmitry Chestnykh wrote:
>> Error: Database error: unable to op
> Error: Database error: unable to open database file
> CREATE TEMP TABLE onremote(rid INTEGER PRIMARY KEY);
Check permissions and ownership of fossil repository file. Are your web process
allowed to write to this file?
--
Dmitry Chestnykh
___
I'm trying to push changes to a central fossil repository and I get the
following error:
Error: Database error: unable to open database file
CREATE TEMP TABLE onremote(rid INTEGER PRIMARY KEY);
The fossil server is running with xinetd. The user that runs the fossil
process owns the r
7 matches
Mail list logo
