[Digikam-users] connectiontest in use, inotify limit

Teemu Rytilahti tpr at iki.fi
Mon Feb 17 23:51:41 GMT 2014


Teemu Rytilahti wrote:

Ah, sorry. Just realized that this is the users list, so I'm going to put 
the things in user-understandable format.

>> #> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is
>> #> still in use, all queries will cease to work.
> 
> This one has something to do with the database backend and is happening to
> everyone I think, it's a bug I'd assume and may cause some weird effects,
> but I haven't noticed any (using sqlite here).

I think this is just used to check if the connection to the database (or in 
case of sqlite, to the file) can be estabilished and that Digikam can make 
the modifications there. So it's probably not an issue.

>> digikam(14981)/digikam (core): Reached inotify limit
> 
> This one just means that the limit for inotify handles is most likely full
> (or kernel failed to allocate resources for it). This could also be a bug,
> I'm not sure whether inotify is able to watch directories recursively, but
> at the moment the watches are being set per album directory. And that most
> likely causes problems, if you have a lot of albums and/or sub-albums.
> 
> sysctl fs.inotify.max_user_watches will give you how many handles is
> possible to have, you can also change that value.

And this means that there are too many folders in the collection, so a new 
directory could not be added to the list of watched folders. That means that 
new items (or new folders) appearing inside that can not be monitored for 
changes (new files, removed files).

-- 
Best Regards,
Teemu Rytilahti





More information about the Digikam-users mailing list