Hi,
no there is currently no (easy) way to avoid a loose of data.
It is ticketed under 2954 (http://redmine.yorba.org/issues/2954). SO if
you have any ideas for an improvement you could write down your thoughts
there.
Some days back there was already the same whish:
Supporting Multiple File-Folders:
- (1) Support more than one directory as file-repository
- (2) Support easy change of such repositories from one place to another
(e.g. files must be shipped from one disk to another)
- (3) Support changable media
[ all these three might be possible, if the databases are held locally to the
folders where the pictures reside; the shotwell-index then is a collection
of links (or include's) to (of) the many possible picture-directories.
(1)...(3) can be done via shotwell including/linking-in
picture-collections
as seperated files-plus-database-combinations;
shotwell-index then would be a meta-index that points to
directories of picture-files and a database in the "root"
of each of those picture-directories (like mounting-in a
complete repository
that also contains the index) ]
Jonas
Am 16.08.2011 13:28, schrieb Francisco Borges:
Hi,
I use Shotwell with an image library mounted over NFS (the pictures are
stored in a NAS).
Sometimes the NAS will be off line, or coming up, or NFS will just hiccup.
In such cases, Shotwell seems to lose all library settings, and when the NFS
gets mounted it needs to re-import all images.
Is there any way to avoid this "lose all library state if NFS share is not
mounted"?
Kind regards,
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
