Avahi - Revision history

Nathanhammond: Note an issue in installing via command line.

2012-01-14T11:35:20Z

Note an issue in installing via command line.

Nathanhammond: Update upstart script for command line installation.

2012-01-14T11:30:03Z

Update upstart script for command line installation.

Wrea: Minor edits, referencing avahi being in repo

2011-12-28T01:07:02Z

Minor edits, referencing avahi being in repo

Drahgon: /* Current Issues */

2011-01-15T18:20:58Z

Current Issues

Drahgon: /* Current Issues */

2011-01-15T18:20:37Z

Current Issues

Drahgon: /* Avahi Installation */

2011-01-15T18:19:10Z

Avahi Installation

Drahgon: /* Avahi Installation */

2011-01-15T18:16:48Z

Avahi Installation

Drahgon: /* Avahi Installation */

2011-01-15T18:16:08Z

Avahi Installation

Drahgon: /* Avahi Installation */

2011-01-15T18:15:19Z

Avahi Installation

Drahgon: /* Avahi Installation */

2011-01-15T18:14:47Z

Avahi Installation

← Older revision		Revision as of 11:35, 14 January 2012
Line 109:		Line 109:
	* The ipkg binary of Avahi attempts to find the dbus socket at <tt>/opt/var/run/dbus/system_bus_socket</tt>, but the Pre's dbus socket is at <tt>/var/run/dbus/system_bus_socket</tt>. I have detailed a solution by running Avahi with root privileges however an approach which allow it to run after dropping root privileges is preferred.		* The ipkg binary of Avahi attempts to find the dbus socket at <tt>/opt/var/run/dbus/system_bus_socket</tt>, but the Pre's dbus socket is at <tt>/var/run/dbus/system_bus_socket</tt>. I have detailed a solution by running Avahi with root privileges however an approach which allow it to run after dropping root privileges is preferred.
	* The avahi-daemon seems to have issues keeping the mDNS name resolution running for more than a few minutes. I don't know if this is a power management issue or something else at this point.		* The avahi-daemon seems to have issues keeping the mDNS name resolution running for more than a few minutes. I don't know if this is a power management issue or something else at this point.
		+	* The command line install approach may result in your device appearing at '''hostname-4.local''' due to avahi-daemon believing that your hostname is already claimed on the first run only.

@@ Line 72: / Line 72: @@
   $> chmod 755 /opt/etc/init.d/S60avahi
-Alternatively, you can create an upstart script at '''/etc/event.d/avahi''':
+Alternatively, you can create an upstart script at '''/etc/event.d/avahi-daemon''':
- start on started PmConnectionManager
+NOTE 1: This script is not being stored in the /opt directory. You may have to replace it after an update, and it may cause problems with your Pre.
-NOTE: This script is not being stored in the /opt directory. You may have to replace it after an update, and it may cause problems with your Pre.
+NOTE 2: You may find your device appearing at '''hostname-4.local''' instead of simply '''hostname.local'''. Restarting avahi-daemon (stop avahi, start avahi) will fix that. You could also figure out the root cause for that problem and address it in a pre-start block in the upstart script.
 ==Connecting via SSH using mDNS==

@@ Line 2: / Line 2: @@
 [http://avahi.org Avahi] is a Linux service for providing multicast-DNS/DNS-SD (also known as [http://en.wikipedia.org/wiki/Bonjour_%28software%29 Bonjour] or mDNS/DNS-SD). Avahi allows for simple service discovery and advertisement on a local network and provides name resolution for all hosts running a mDNS/DNS-SD service.
-Using Avahi allows for easy SSH access over a local wireless network. Once installed and started, users can ssh to their device using their mDNS assigned hostname.
+Using Avahi allows for easy SSH access, among other things, over a local wireless network. Once installed and started, users can ssh to their device using their mDNS assigned hostname.
 ==Avahi Installation==
 First, use novacom to access the Pre and install the Avahi ipkg.
@@ Line 93: / Line 95: @@
 '''Note: The system that you are connecting from MUST have a mDNS service also running, else the hostname will not resolve'''
-==Current Issues==
+==Current Issues on the Pre==
 * The ipkg binary of Avahi attempts to find the dbus socket at <tt>/opt/var/run/dbus/system_bus_socket</tt>, but the Pre's dbus socket is at <tt>/var/run/dbus/system_bus_socket</tt>. I have detailed a solution by running Avahi with root privileges however an approach which allow it to run after dropping root privileges is preferred.
 * The avahi-daemon seems to have issues keeping the mDNS name resolution running for more than a few minutes. I don't know if this is a power management issue or something else at this point.

@@ Line 95: / Line 95: @@
 ==Current Issues==
-* The ipkg binary of Avahi attempts to find the dbus socket at <tt>/opt/var/run/dbus/system_bus_socket</tt>, but the Pre's dbus socket is at <tt>/var/run/dbus/system_bus_socket</tt>. I have detailed a solution by running the avahi with root privileges however an approach which allow it to run after dropping root privileges is preferred.
+* The ipkg binary of Avahi attempts to find the dbus socket at <tt>/opt/var/run/dbus/system_bus_socket</tt>, but the Pre's dbus socket is at <tt>/var/run/dbus/system_bus_socket</tt>. I have detailed a solution by running Avahi with root privileges however an approach which allow it to run after dropping root privileges is preferred.
 * The avahi-daemon seems to have issues keeping the mDNS name resolution running for more than a few minutes. I don't know if this is a power management issue or something else at this point.

@@ Line 95: / Line 95: @@
 ==Current Issues==
-* The ipkg binary of Avahi attempts to find the dbus socket at <tt>/opt/var/run/dbus/system_bus_socket</tt>, but the Pre's dbus socket is at <tt>/var/run/dbus/system_bus_socket</tt>. I haven't investigated tying these two together too much, but the expanded functionality of accessing mDNS via dbus is preferred.
+* The ipkg binary of Avahi attempts to find the dbus socket at <tt>/opt/var/run/dbus/system_bus_socket</tt>, but the Pre's dbus socket is at <tt>/var/run/dbus/system_bus_socket</tt>. I have detailed a solution by running the avahi with root privileges however an approach which allow it to run after dropping root privileges is preferred.
 * The avahi-daemon seems to have issues keeping the mDNS name resolution running for more than a few minutes. I don't know if this is a power management issue or something else at this point.

@@ Line 7: / Line 7: @@
 ==Avahi Installation==
-First, mount the root filesystem as writable and install the Avahi ipkg.
+First, use novacom to access the Pre and install the Avahi ipkg.
   $> sudo /opt/bin/ipkg-opt install avahi
@@ Line 38: / Line 37: @@
 At this point, the Avahi daemon can be started with root privileges and dbus support with the following command:
-  $> sudo /opt/sbin/avahi-daemon --no-drop-root
+  $> /opt/sbin/avahi-daemon --no-drop-root
 If you disabled dbus support however it is recommended to run Avahi daemon without root privileges using the following command:
-  $> sudo /opt/sbin/avahi-daemon
+  $> /opt/sbin/avahi-daemon
@@ Line 69: / Line 68: @@
 Make sure you set the startup script to executable:
-  $> sudo chmod 755 /opt/etc/init.d/S60avahi
+  $> chmod 755 /opt/etc/init.d/S60avahi
 Alternatively, you can create an upstart script at '''/etc/event.d/avahi''':

← Older revision		Revision as of 18:16, 15 January 2011
Line 18:		Line 18:


−	Avahi currently attempts to access a different dbus system socket than the one provided by the Pre's dbus, it is possible to start Avahi with dbus support by creating a symbolic link to from to palm dbus directory to the /opt dbus directory and starting avahi daemon with root privileges. According to the Avahi website, however running avahi-daemon with root privileges is not recommended.	+	Avahi currently attempts to access a different dbus system socket than the one provided by the Pre's dbus, it is possible to start Avahi with dbus support by creating a symbolic link from palm dbus directory to the /opt dbus directory and starting avahi daemon with root privileges. According to the Avahi website, however running avahi-daemon with root privileges is not recommended.

	The following command will create a symbolic link to /opt dbus directory to palm dbus directory:		The following command will create a symbolic link to /opt dbus directory to palm dbus directory:

← Older revision		Revision as of 18:15, 15 January 2011
Line 11:		Line 11:
	$> sudo mount -o remount,rw /		$> sudo mount -o remount,rw /
	$> sudo /opt/bin/ipkg-opt install avahi		$> sudo /opt/bin/ipkg-opt install avahi
−
−	~~It is possible to enable allow Avahi to run with with dbus support.~~

← Older revision		Revision as of 18:14, 15 January 2011
Line 25:		Line 25:

	ln -s /var/run/dbus /opt/var/run/dbus		ln -s /var/run/dbus /opt/var/run/dbus
		+

	if preferred avahi can be be ran without dbus support by editing <tt>/opt/etc/avahi/avahi-daemon.conf</tt> and make the following change:		if preferred avahi can be be ran without dbus support by editing <tt>/opt/etc/avahi/avahi-daemon.conf</tt> and make the following change: