1 |
Hi, |
2 |
|
3 |
Last 2 lines of your log: |
4 |
Unable to initialize inotify: |
5 |
> > Function not implemented |
6 |
|
7 |
inotify comes from kernel, in my config: |
8 |
|
9 |
elwood linux # zcat /proc/config.gz |grep -i notify |
10 |
CONFIG_INOTIFY=y |
11 |
CONFIG_INOTIFY_USER=y |
12 |
CONFIG_DNOTIFY=y |
13 |
|
14 |
in menuconfig: |
15 |
|
16 |
┌─────── File systems |
17 |
|
18 |
[...] |
19 |
|
20 |
[*] Inotify file change notification support |
21 |
|
22 |
[*] Inotify support for userspace |
23 |
|
24 |
bye bye |
25 |
|
26 |
|
27 |
Mick ha scritto: |
28 |
> On Saturday 04 August 2007 11:21, Mick wrote: |
29 |
>> On Tuesday 17 July 2007 10:52, Alessandro del Gallo wrote: |
30 |
>>> Mick ha scritto: |
31 |
>>>> On Monday 16 July 2007 10:26, Alessandro del Gallo wrote: |
32 |
>>>>> Mick ha scritto: |
33 |
>>>>>> Hi All, |
34 |
>>>>>> |
35 |
>>>>>> I noticed on a box of mine that hald won't start: |
36 |
>>>>>> ========================================== |
37 |
>>>>>> # /etc/init.d/hald restart |
38 |
>>>>>> * Starting Hardware Abstraction Layer daemon ... [ !! ] |
39 |
>>>>>> ========================================== |
40 |
>>>>>> |
41 |
>>>>>> Confusingly, the logs don't show anything. How do I troubleshoot |
42 |
>>>>>> this? |
43 |
>>>>> I had the same problem: |
44 |
>>>>> |
45 |
>>>>> hald was sucking 99% cpu, removables devices didn't work |
46 |
>>>>> and launching hald from terminal with the option "hald --daemon=no |
47 |
>>>>> --verbose=yes" i discovered it was on a infinite loop echo-ing |
48 |
>>>>> something about rules so I got in /etc/udev/rules.d |
49 |
>>>>> and found (by probing one by one) 99-libgphoto2.rules that |
50 |
>>>>> was HALS's murder. |
51 |
>>>> Thank you Alessandro, what do you mean by probing - how did you probe |
52 |
>>>> them? |
53 |
>>> moving it to /tmp and restart hald, |
54 |
>>> becouse the error I got when launching |
55 |
>>> # hald --daemon=no --verbose=yes |
56 |
>>> is "Unhandled Rule (0)" |
57 |
>>> so deleting the rules (delete de rule, start hald, if it doesn't |
58 |
>>> works put the rule back , and move another) from etc/udev/rules.d |
59 |
>>> I debugged the problem, the bad rule was owned by gphoto2 |
60 |
>> I've had a chance to get back to this machine and this is what it is |
61 |
>> showing: ========================================== |
62 |
>> # hald --daemon=no --verbose=yes |
63 |
>> 11:16:08.930 [I] hald.c:533: hal 0.5.9 |
64 |
>> 11:16:08.931 [I] hald.c:598: Will not daemonize |
65 |
>> 11:16:08.945 [I] hald_dbus.c:4807: local server is listening at |
66 |
>> unix:abstract=/var/run/hald/dbus-1LzyssbMzl,guid=faadd829b7aaff57dce0510046 |
67 |
>> b451e8 11:16:09.174 [I] hald_runner.c:299: Runner has pid 31241 |
68 |
>> 11:16:09.180 [W] ci-tracker.c:200: Could not get uid for connection: |
69 |
>> org.freedesktop.DBus.Error.NameHasNoOwner Could not get UID of |
70 |
>> name 'org.freedesktop.DBus': no such name |
71 |
>> 11:16:09.181 [E] hald_dbus.c:4462: Cannot get caller info for |
72 |
>> org.freedesktop.DBus |
73 |
>> Runner started - allowed paths |
74 |
>> are '/usr/libexec:/usr/lib/hal/scripts:/usr/bin' |
75 |
>> 11:16:09.196 [I] hald_runner.c:180: runner connection is 0x8096988 |
76 |
>> 11:16:09.330 [I] mmap_cache.c:251: cache mtime is 1184442336 |
77 |
>> *** [DIE] osspec.c:watch_fdi_files():349 : Unable to initialize inotify: |
78 |
>> Function not implemented |
79 |
>> ========================================== |
80 |
>> |
81 |
>> What do you make of this? |
82 |
> |
83 |
> I removed /usr/share/hal and tried to remerge it. It complained that I "MUST" |
84 |
> compile pciutils without the zlib flag. Not sure why pciutils has the zlib |
85 |
> flag as a default, but if it is causing a problem with hal shouldn't it be |
86 |
> removed? |
87 |
> |
88 |
> Anyway, after masking zlib for pciutils and remerging both packages it now |
89 |
> seems to be working again . . . |
90 |
> |
91 |
> Thanks for your suggestions. |
92 |
|
93 |
-- |
94 |
gentoo-user@g.o mailing list |