[fossil-users] Suggested addition to the documentation.

2009-08-09 Thread Michael Richter
I wrestled with *xinetd* today to get a Fossil repository accessible. The current docs give the *inetd* line for a fossil service but do not document *xinetd*. I recommend adding the following to the docs in the appropriate place. (I'd do it myself, but I can't remember my login ID/password for

Re: [fossil-users] fossil commit on afs volume disk i/o error

2009-08-09 Thread Matthias Teege
On Sun, Aug 9, 2009 at 7:33 PM, D. Richard Hipp wrote: Hello, thanks for your answer. >     export FOSSIL_VFS=unix-none >     export FOSSIL_VFS=unix-dotfile > > The first command above will disable file locking completely.  The > second will shift fossil to use dot-file locking instead of posix

Re: [fossil-users] fossil commit on afs volume disk i/o error

2009-08-09 Thread Stephan Beal
On Sun, Aug 9, 2009 at 7:56 PM, D. Richard Hipp wrote: > The per-repository options are stored in an SQLite database. So we > cannot read the per-repository options until after we have made the > decision of what kind of locking to use with SQLite databases. > Bummer /smack forehead. Doh,

Re: [fossil-users] fossil commit on afs volume disk i/o error

2009-08-09 Thread D. Richard Hipp
On Aug 9, 2009, at 1:49 PM, Stephan Beal wrote: > On Sun, Aug 9, 2009 at 7:33 PM, D. Richard Hipp wrote: > Note that you will need to set the FOSSIL_VFS environment variable in > each shell before you start using fossil in that shell. > > Would that be better placed as a per-repository option?

Re: [fossil-users] fossil commit on afs volume disk i/o error

2009-08-09 Thread Stephan Beal
On Sun, Aug 9, 2009 at 7:33 PM, D. Richard Hipp wrote: > Note that you will need to set the FOSSIL_VFS environment variable in > each shell before you start using fossil in that shell. Would that be better placed as a per-repository option? -- - stephan beal http://wanderinghorse.net/home

Re: [fossil-users] fossil commit on afs volume disk i/o error

2009-08-09 Thread D. Richard Hipp
On Aug 9, 2009, at 1:17 PM, D. Richard Hipp wrote: > > On Aug 9, 2009, at 12:40 PM, Matthias Teege wrote: > >> >> New_Version: 810d89fcb62d6821cd20e6b6b25b0bb112370b2c >> fossil: disk I/O error >> COMMIT > > My guess is that this has something to do with AFS not supporting > posix advisory locks..

Re: [fossil-users] fossil commit on afs volume disk i/o error

2009-08-09 Thread D. Richard Hipp
On Aug 9, 2009, at 12:40 PM, Matthias Teege wrote: > Moin, > > I have a small project on an AFS file system. I fossil commit gives > me an > disk I/O error. > > New_Version: 810d89fcb62d6821cd20e6b6b25b0bb112370b2c > fossil: disk I/O error > COMMIT > > There are also two new files, manifest and

[fossil-users] fossil commit on afs volume disk i/o error

2009-08-09 Thread Matthias Teege
Moin, I have a small project on an AFS file system. I fossil commit gives me an disk I/O error. New_Version: 810d89fcb62d6821cd20e6b6b25b0bb112370b2c fossil: disk I/O error COMMIT There are also two new files, manifest and manifest.uuid in the directory. I think the checkin is ok but the disk i/

Re: [fossil-users] Problem under Linux with PHP web interface

2009-08-09 Thread D. Richard Hipp
On Aug 9, 2009, at 6:03 AM, Wim Paulussen wrote: > LS, > > I have a basic setup for a webinterface to manage my fossil > repository written in PHP. Currently 'add' , 'delete' and 'commit' > work as expected. I have been testing first under Windows (Vista) > which works like a charm. While t

[fossil-users] Problem under Linux with PHP web interface

2009-08-09 Thread Wim Paulussen
LS, I have a basic setup for a webinterface to manage my fossil repository written in PHP. Currently 'add' , 'delete' and 'commit' work as expected. I have been testing first under Windows (Vista) which works like a charm. While trying to do the same under linux I get the following error : 'fo