On Apr 20, 2014 6:46 PM, "Ed Greshko" <ed.greshko@greshko.com> wrote:
>
> 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 value if you have KDE or installed a package that pulled nepomuk-core as a dependency.
> >
> > [1]https://bugzilla.redhat.com/show_bug.cgi?id=858271
> >
>
> I have another question......
>
> I just did a "yum erase nepomuk-core" on a system and /usr/lib/sysctl.d/97-kde-nepomuk-filewatch-inotify.conf was removed since it was owned by nepomuk-core.
>
> Upon reboot of the system ....
>
> [egreshko@f20kde ~]$ ls /usr/lib/sysctl.d/
> 00-system.conf  50-default.conf  libvirtd.conf
> [egreshko@f20kde ~]$ cat /proc/sys/fs/inotify/max_user_watches
> 524288
>
> So, it seems that file isn't really needed in F20 at this time to raise the limit?
>
>
> --
> Getting tired of non-Fedora discussions and self-serving posts
> --
> users mailing list
> users@lists.fedoraproject.org
> 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

Nepomuk has been deprecated in favor of Baloo. Wonder if KDE guys still plan to ship the higher limit.