Am 29.05.2009, 17:42 Uhr, schrieb David Paleino <[email protected]>:
>> Now Carlos' and my problem is, that by >> >> <busconfig> >> <policy user="root"> >> <allow own="org.wicd.daemon"/> >> <allow send_destination="org.wicd.daemon"/> >> <allow send_interface="org.wicd.daemon"/> >> </policy> >> <policy at_console="true"> >> <deny own="org.wicd.daemon"/> >> <allow send_destination="org.wicd.daemon"/> >> <allow send_interface="org.wicd.daemon"/> >> </policy> >> [..] >> >> denying to own the service name from console prompts means, even as root >> I cannot start the wicd-daemon via >> >> Debian:~# /etc/init.d/wicd start > > I can't reproduce this, sorry: Hi David, I am sorry I have bothered you, I can't reproduce it either. I have no idea what was wrong but "my bug" happened independently on two laptops last week (before I reported it), with the same dbus-error message about denying to own the the service name when trying to start the service. >From what I read in the dbus-specification >(http://dbus.freedesktop.org/doc/dbus-daemon.1.html) it occured to me, that >when starting the service as root on the console both policy brackets apply >and the second deny overwrites the first allow stanza. But this is eventually >not the case. Since I cannot reproduce last week's incidence, I'll just ignore >it. By the way, denial of ownership is enabled by default. /etc/dbus-1/system.conf: [..] <!-- Holes must be punched in service configuration files for name ownership and sending method calls --> <deny own="*"/> <deny send_type="method_call"/> [..] So the deny-tag should be redundant anyway. Thanks for your patience, Thorsten -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
