Thats because avahi-discover-standalone uses the core avahi libraries directly (like avahi-daemon) and not the dbus interface to avahi-daemon.
Cheers, Trent On Thu, Jun 08, 2006 at 11:21:24AM -0400, Nicholas Andrews wrote: > avahi-discover-standalone works, though. > > On 6/8/06, Nicholas Andrews <[EMAIL PROTECTED]> wrote: > >avahi-0.6.10, configured with all defaults except no QT bindings, no > >mono, and no python. > > > >dbus-0.61, default configuration > > > >libdaemon-0.10, default configuration > > > >On debian stable, I compiled the example with the following command: > > > >gcc client-browse-services.c `pkg-config avahi-client --cflags --libs` > > > >There were no warnings and no errors. When I run the executable, I get > >the following error: "Failed to create client: An unexpected DBUS > >error occured" > > > >Both dbus-daemon and dbus-start appear to be running, however I don't > >see the avahi-daemon. If I try to start it again with "avahi-daemon" > >it fails with: > > > >dbus_bus_get(): Failed to connect to socket > >/usr/local/var/run/dbus/system_bus_socket: No such file or directory > >WARNING: Failed to contact D-BUS daemon. > > > >Am I missing a configuration step? > > > >Cheers! > > > >-Nick > > > _______________________________________________ > avahi mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/avahi -- Trent Lloyd <[EMAIL PROTECTED]> Bur.st Networking Inc. _______________________________________________ avahi mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/avahi
