On 20 April 2014 10:28, M. Fioretti <mfioretti@xxxxxxxxxxx> 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 calculatedok that's why then. So the only thing I need, if anything, is further
> 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 8192.
confirmation that increasing it on F17 would not cause problems. I'll
wait until tomorrow for further comments and then "risk" the increase
:-)
Marco
--
M. Fioretti http://mfioretti.com http://stop.zona-m.net
Your own civil rights and the quality of your life heavily depend on how
software is used *around* you
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 value if you have KDE or installed a package that pulled nepomuk-core as a dependency.
--
Ahmad Samir
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
