I'm not saying that it's necessarily a bug, but it would be nice if during the VACUUM'ing phase of the
fossil rebuild a_huge.fossilrepository --vacuum --compress --cluster the Fossil Web GUI would say that the repository is currently being rebuilt in stead of saying ----citation--start------------- SQLITE_BUSY: database is locked SQLITE_MISUSE: API called with NULL prepared statement SQLITE_MISUSE: misuse at line 77320 of [47cf83a068] SQLITE_BUSY: database is locked SQLITE_MISUSE: API called with NULL prepared statement SQLITE_MISUSE: misuse at line 77320 of [47cf83a068] SQLITE_BUSY: database is locked SQLITE_MISUSE: API called with NULL prepared statement SQLITE_MISUSE: misuse at line 77320 of [47cf83a068] SQLITE_BUSY: database is locked SQLITE_MISUSE: API called with NULL prepared statement SQLITE_MISUSE: misuse at line 77320 of [47cf83a068] SQLITE_BUSY: database is locked SQLITE_MISUSE: API called with NULL prepared statement SQLITE_MISUSE: misuse at line 77320 of [47cf83a068] SQLITE_BUSY: database is locked Database Error database is locked: {REPLACE INTO config(name,value,mtime) VALUES('hash-policy',2,now())} ----citation--end--------------- I was logged in as administrator from the web GUI and the rebuild command was started from an ssh console. The Fossil version is/was 2.3 uname -a FreeBSD capella.elkdata.ee 10.3-RELEASE-p17 FreeBSD 10.3-RELEASE-p17 #0: Fri Mar 3 18:23:48 EET 2017 r...@capella.elkdata.ee:/usr/obj/usr/src/sys/ELKDATA amd64 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users