On May 9, 2018, at 12:44 PM, Florian Balmer <florian.bal...@gmail.com> wrote: > > With Fossil 2.6, sometimes there's *.fossil-shm and *.fossil-wal files left > behind in the directory where the repository databases are stored. > > This happens if an unversioned file is accessed through the /uv web > interface for the second time (or more)
If “fossil server” or “fossil ui” is still running in the background, then I would fully expect the WAL and SHM files to still be around. The worrying case is when they’re left behind after the SQLite-based process that created them has died. > I'm aware this is not dangerous, as SQLite will recover any information > from the leftover files, but nonetheless I'm reporting it. If it’s the case that there are no active Fossil instances while those files are on disk, then yes, it’s good to report this, because it means the SQLite DB connection isn’t being shut down properly. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
