Which collection option for NFS automounts?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Which collection option for NFS automounts?

Jonathan Marten-2
Hello all,

After having reorganised my home network I'm planning to set up digiKam to
index and tag everything from scratch, since I did some experimenting but no
serious work with my old setup.  I'm planning to have some collections served
from an NFS server via automounts, i.e. accessing "/shares/photos"
automatically mounts server:/export/photos at that path.

My question is: in this case, is there any difference between entering this
path as either a "Local Collection" or a "Collection on Network Shares" in
digiKam?  The path would be the same in both cases.  There is some possibility
that the network share may not be accessible if the server were to go down,
but assuming that this does not happen, is there any practical difference
between the two options?  If there is, which one would it be best to use?

I know that the database has problems being on an NFS share, so will ensure
that this is on a local path.

Any advice will be appreciated!

--
Jonathan Marten                         http://www.keelhaul.demon.co.uk
Twickenham, UK                          [hidden email]

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Which collection option for NFS automounts?

Manuel Bock
Hi Jonathan,

running a relatively similiar setup, I would recommend adding that directory
as a network share. As far as I understood, digikam is otherwise handling the
pictures in that subfolder as have been deleted outside of dk if the share
isn't mounted and it will start removing the corresponding database enties on
the next folder scan.

You could deactivate the automatic scan at startup, but still ...

regards
Manuel

Am Samstag, 2. März 2013, 16:08:41 schrieb Jonathan Marten:

> Hello all,
>
> After having reorganised my home network I'm planning to set up digiKam to
> index and tag everything from scratch, since I did some experimenting but no
> serious work with my old setup.  I'm planning to have some collections
> served from an NFS server via automounts, i.e. accessing "/shares/photos"
> automatically mounts server:/export/photos at that path.
>
> My question is: in this case, is there any difference between entering this
> path as either a "Local Collection" or a "Collection on Network Shares" in
> digiKam?  The path would be the same in both cases.  There is some
> possibility that the network share may not be accessible if the server were
> to go down, but assuming that this does not happen, is there any practical
> difference between the two options?  If there is, which one would it be
> best to use?
>
> I know that the database has problems being on an NFS share, so will ensure
> that this is on a local path.
>
> Any advice will be appreciated!
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Which collection option for NFS automounts?

Jonathan Marten-2
Thanks for your advice Manuel, I'll try this option.  I assume that there
won't be any problems with things getting removed from the database on any
scan (whether automatic or manual) if the network folder is actually online
and accessible at the time.  Which I expect it to be, so it should work.

Best regards,
  Jonathan




On Sunday 03 March 2013 15:24:11 Manuel Bock wrote:

> Hi Jonathan,
>
> running a relatively similiar setup, I would recommend adding that directory
> as a network share. As far as I understood, digikam is otherwise handling
> the pictures in that subfolder as have been deleted outside of dk if the
> share isn't mounted and it will start removing the corresponding database
> enties on the next folder scan.
>
> You could deactivate the automatic scan at startup, but still ...
>
> regards
> Manuel
>
> Am Samstag, 2. März 2013, 16:08:41 schrieb Jonathan Marten:
> > Hello all,
> >
> > After having reorganised my home network I'm planning to set up digiKam to
> > index and tag everything from scratch, since I did some experimenting but
> > no serious work with my old setup.  I'm planning to have some collections
> > served from an NFS server via automounts, i.e. accessing "/shares/photos"
> > automatically mounts server:/export/photos at that path.
> >
> > My question is: in this case, is there any difference between entering
> > this
> > path as either a "Local Collection" or a "Collection on Network Shares" in
> > digiKam?  The path would be the same in both cases.  There is some
> > possibility that the network share may not be accessible if the server
> > were
> > to go down, but assuming that this does not happen, is there any practical
> > difference between the two options?  If there is, which one would it be
> > best to use?
> >
> > I know that the database has problems being on an NFS share, so will
> > ensure
> > that this is on a local path.
> >
> > Any advice will be appreciated!
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
--
Jonathan Marten                         http://www.keelhaul.demon.co.uk
Twickenham, UK                          [hidden email]

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users