On Tue, Sep 24, 2013 at 12:43 PM, Krister Johnson <krist...@gmail.com>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 apply (not on NFS). The fossil executable is located at /bin > and I'm running "fossil server /etc/fossil/repo" from a script in > /etc/init.d/. I've tried rebooting and restarting fossil. > > Why am I getting this warning? Thanks guys. > 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 the chroot jail. If the database file is open prior to entering the chroot jail, it needs to be closed prior to entry then reopened afterwards. The warning is generated because Fossil (actually, SQLite) really does see the repository file as having been moved. Of course, the repository didn't move, but the root of the filesystem did. And since SQLite and Fossil measure the location of files relative to the root of the filesystem it certainly looks to them as if the repository file has moved. Probably this is coming up now because you are the first person to actually try to run "fossil server" as root since that warning message was added. Most people run Fossil server using CGI, SCGI, or xinetd, I think, or else they run them as an unprivileged user. 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. (Stephan's email just arrived.) Or, the problem might be due to a symlink. -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
