On Dec 13, 2017, at 1:37 PM, Richard Hipp <d...@sqlite.org> wrote:
>
> On 12/13/17, Warren Young <war...@etr-usa.com> wrote:
>> I just tried to rebuild a Fossil repo that I’d lost permission to read due
>> to some sysadmin silliness, and got spammed by this in a rapid loop:
>>
>> PRAGMA database_list
>> SQLITE_CANTOPEN: cannot open file at line 36229 of [1a584e4999]
>> SQLITE_CANTOPEN: os_unix.c:36229: (2) open(/nunya/binness.fossil-wal) - No
>> such file or directory
>> SQLITE_CANTOPEN: unable to open database file
>> fossil: unable to open database file
>
> Trunk now fixes this problem, and offers improved error message to
> help diagnose the problem, should it come up again.
Thanks, it’s better, though it does still repeat itself 8x:
SQLITE_CANTOPEN: cannot open file at line 36506 of [1c0aa919ee]
SQLITE_CANTOPEN: os_unix.c:36506: (2) open(/nunya/binness.fossil-wal) - No
such file or directory
SQLITE_READONLY: database is in a read-only directory
Shouldn’t that last line be fatal, stopping the loop?
To reproduce it:
$ sudo chown -R 42 /museum
$ fossil rebuild -R /museum/foo.fossil
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
