On 04/20/14 13:49, M. Fioretti wrote:
Greetings,
a while ago, I noticed that on my Fedora box digiKam would not load
and display picture galleries anymore, and when launched from the
prompt would produce this message:
digikam(14981)/digikam (core): Reached inotify limit
which IIUC means
On Sun, Apr 20, 2014 14:11:24 PM +0800, Ed Greshko wrote:
I don't know how the system sets this value. 8192 seems rather small to me.
good point, thanks. This, in fact, is a side question that I forgot to
ask in my original email: what are the criteria or rule of thumb to
calculate which
On 04/20/14 14:09, M. Fioretti wrote:
On Sun, Apr 20, 2014 14:11:24 PM +0800, Ed Greshko wrote:
I don't know how the system sets this value. 8192 seems rather small to me.
good point, thanks. This, in fact, is a side question that I forgot to
ask in my original email: what are the criteria or
On Sun, Apr 20, 2014 14:40:07 PM +0800, Ed Greshko wrote:
One silly question.
What version of Fedora are you running. I found a message on the mailing
lists back in 2010 which, from a reliable source, indicated
this is happening on an F17 box. It **is** scheduled to be moved
On 04/20/14 15:08, M. Fioretti wrote:
On Sun, Apr 20, 2014 14:40:07 PM +0800, Ed Greshko wrote:
One silly question.
What version of Fedora are you running. I found a message on the
mailing lists back in 2010 which, from a reliable source, indicated
this is happening on an F17
On Sun, Apr 20, 2014 16:24:08 PM +0800, Ed Greshko wrote:
On 04/20/14 15:08, M. Fioretti wrote:
FWIW, everything I've seen indicates this value is not calculated
but configured when the kernel is compiled. I just happen to have
an old F17 disk and created a VM. As expected, it is set to
On 04/20/14 16:28, M. Fioretti wrote:
ok that's why then. So the only thing I need, if anything, is further
confirmation that increasing it on F17 would not cause problems. I'll
wait until tomorrow for further comments and then risk the increase
:-)
FWIW, I just made the change in
On 20 April 2014 10:28, M. Fioretti mfiore...@nexaima.net wrote:
On Sun, Apr 20, 2014 16:24:08 PM +0800, Ed Greshko wrote:
On 04/20/14 15:08, M. Fioretti wrote:
FWIW, everything I've seen indicates this value is not calculated
but configured when the kernel is compiled. I just happen to
On 04/20/14 20:51, Ahmad Samir wrote:
The value of fs.inotify.max_user_watches was increased in F18, and later
releases, due to this bug[1] in nepomuk. It's configured by
/usr/lib/sysctl.d/97-kde-nepomuk-filewatch-inotify.conf which is installed by
nepomuk-core, so ideally you'd get that
On 04/20/14 21:38, Ahmad Samir wrote:
/usr/lib/sysctl.d/97-kde-nepomuk-filewatch-inotify.conf is included in the
initramfs by dracut when a kernel is installed/updated. Check `lsinitrd
/boot/initramfs-$(uname -r).img | grep sysctl`.
So in effect you'd have to re-create the initramfs after
10 matches
Mail list logo
