[Shotwell] NFS library question

[Thomas Novin]

On Wed, Aug 17, 2011 at 9:31 AM, Colin Law <clanlaw at googlemail.com> wrote:
> On 16 August 2011 12:28, Francisco Borges <francisco.borges at gmail.com> wrote:
>> 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"?
>
> Hi, I am new to Shotwell so my facts may be wrong, but I seem to
> remember that one can put the Shotwell database in a non-standard
> location.  If one put the database on the same drive as the photos
> then if the drive was not mounted Shotwell would also not have access
> to the database, so presumably could not remove its knowledge of the
> photos.  I have not tried it but perhaps Showell would just fail to
> start in some way.  Then if the drive is mounted and Shotwell is
> re-started perhaps it would find the db and all would be well.  Is
> that a valid workaround for the problem or is my logic flawed?

This is pretty much what I have done with F-spot. I had the db stored
on the same path as the photos and we were two users sharing that
installation.

When F-spot started it first checked if the db was readable, if not,
it would send an error and close.

The same method would most probably be applicable to Shotwell. This
what I will do as a workaround at least..

Rgds