1 |
On Friday, August 21, 2015 10:56:58 AM Francisco Ares wrote: |
2 |
> 2015-08-21 10:49 GMT-03:00 Francisco Ares <frares@×××××.com>: |
3 |
> > 2015-08-21 10:31 GMT-03:00 J. Roeleveld <joost@××××××××.org>: |
4 |
> >> On Friday, August 21, 2015 10:06:15 AM Francisco Ares wrote: |
5 |
> >> > Hi, |
6 |
> >> > |
7 |
> >> > In fact, I can only suppose there's something related to changing from |
8 |
> >> > nepomuk to baloo: |
9 |
> >> > |
10 |
> >> > Now, every time I log in, a window pops up asking for root password. |
11 |
> >> |
12 |
> >> The |
13 |
> >> |
14 |
> >> > window title is "PolicyKit - KDE" and pressing the button "Details", it |
15 |
> >> > shows: |
16 |
> >> > |
17 |
> >> > Action: Folder Watch Limit |
18 |
> >> > polkit.subject-pid: 5254 |
19 |
> >> > polkit.caller-pid: 6699 |
20 |
> >> > |
21 |
> >> > Looking for those PIDs: |
22 |
> >> > |
23 |
> >> > ~ $ ps -A | grep 5254 |
24 |
> >> > |
25 |
> >> > 5254 ? 00:00:07 baloo_file |
26 |
> >> > |
27 |
> >> > and PID 6699 doesn't show up any more, probably the process has already |
28 |
> >> > ended. |
29 |
> >> > |
30 |
> >> > Did I miss something? How do I set up Baloo? Looking on the net, I only |
31 |
> >> > found how to set up a file ~/.kde4/share/config/nepomukserverrc (that |
32 |
> >> |
33 |
> >> was |
34 |
> >> |
35 |
> >> > nonexistent, which seemed strange), is there something else regarding |
36 |
> >> |
37 |
> >> the |
38 |
> >> |
39 |
> >> > database it might be willing to use? |
40 |
> >> |
41 |
> >> Nepomuk, and now Baloo, want to open file-watchers on your system to get |
42 |
> >> change-notifications directly from the kernel (filesystem driver), |
43 |
> >> instead of |
44 |
> >> polling the filesystem. |
45 |
> >> This is actually better, performance wise. |
46 |
> >> |
47 |
> >> To avoid these message, I created the following file a long time ago: |
48 |
> >> |
49 |
> >> % cat /etc/sysctl.d/97-kde-nepomuk-filewatch-inotify.conf |
50 |
> >> fs.inotify.max_user_watches = 65536 |
51 |
> >> |
52 |
> >> Guess I will need to change the name of that file now :) |
53 |
> >> |
54 |
> >> Kind regards, |
55 |
> >> |
56 |
> >> Joost |
57 |
> > |
58 |
> > Thank you, Joost. |
59 |
> > |
60 |
> > Best Regards, |
61 |
> > Francisco |
62 |
> |
63 |
> Checking on the file pointed by Joost, I've found it on my filesystem), but |
64 |
> there is another file, an almost exact copy, for baloo: |
65 |
> |
66 |
> ~ # l /etc/sysctl.d/ |
67 |
> total 28K |
68 |
> drwxr-xr-x 2 root root 4,0K Ago 21 10:50 ./ |
69 |
> drwxr-xr-x 160 root root 12K Ago 21 10:22 ../ |
70 |
> -rw-r--r-- 1 root root 36 Ago 21 09:16 |
71 |
> 97-kde-baloo-filewatch-inotify.conf |
72 |
> |
73 |
> -rw-r--r-- 1 root root 36 Mai 7 2014 |
74 |
> 97-kde-nepomuk-filewatch-inotify.conf |
75 |
> |
76 |
> |
77 |
> ~ # cat /etc/sysctl.d/97-kde-* |
78 |
> fs.inotify.max_user_watches = 65536 |
79 |
> fs.inotify.max_user_watches = 32768 |
80 |
> |
81 |
> |
82 |
> |
83 |
> The first value (65536) is from 97-kde-baloo-filewatch-inotify.conf . The |
84 |
> second (32768) is from 97-kde-nepomuk-filewatch-inotify.conf. |
85 |
> |
86 |
> So, the mystery goes on... |
87 |
> |
88 |
> Thanks, |
89 |
> Francisco |
90 |
|
91 |
what does: |
92 |
% cat /proc/sys/fs/inotify/max_user_watches |
93 |
give you? |
94 |
|
95 |
My guess: 32768 (as that's the last one it will find) |
96 |
On my system I get 65536. |
97 |
|
98 |
I think if you were to remove the nepomuk file, it should work. |
99 |
|
100 |
-- |
101 |
Joost |