Bug 68609 - audio/daapd: pkg-message is incorrect
Summary: audio/daapd: pkg-message is incorrect
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Lars Thegler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-02 19:50 UTC by paul beard
Modified: 2004-07-10 10:50 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description paul beard 2004-07-02 19:50:16 UTC
	pkg-message directs the user to invoke mDNSResponder to activate daapd: that's incorrect.
	It needs to be mDNSPublish. Also the syntax specified is wrong for my version.

Fix: 

This will publish a daapd library called Music on port 3689 using daap over tcp. 
	mDNSPublish Music _daap._tcp 3689
Comment 1 paul beard 2004-07-02 20:31:46 UTC
Also, it appears daapd is linked against the wrong libhttpd or perhaps 
not linked against one at all. These errors (from the FAQ) are 
consistent with what I am seeing:

TROUBLESHOOTING

Q: Does daapd work with iTunes 4.6?

A: It does. Make sure you have at least daapd 0.2.2a. Also make sure 
that daapd is linked against a recent version of libhttpd-persistent 
(at least version g). The following output is an indication that daapd 
uses an earlier version of libhttpd:

192.168.53.69 - - [10/May/2004:12:46:11 CEST] GET 
"daap:/192.168.53.68:3689/server-info" HTTP/1.1 400 0

You should get an output like that instead:

10.0.0.100 - - [12/Jun/2004:12:17:06 CEST] GET "/server-info" HTTP/1.1 
200 132

ldd `which daapd`
/usr/local/bin/daapd:
         libid3tag.so.2 => /usr/local/lib/libid3tag.so.2 (0x28090000)
         libz.so.2 => /usr/lib/libz.so.2 (0x280a0000)
         libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x280ad000)
         libm.so.2 => /usr/lib/libm.so.2 (0x280f2000)
         libc.so.4 => /usr/lib/libc.so.4 (0x2810d000)

--
Paul Beard
<www.paulbeard.org/>
paulbeard [at] mac.com
Comment 2 Oliver Eikemeier freebsd_committer freebsd_triage 2004-07-02 20:49:35 UTC
Responsible Changed
From-To: freebsd-ports-bugs->lth

Over to maintainer
Comment 3 Lars Thegler 2004-07-02 23:04:08 UTC
> 	pkg-message directs the user to invoke mDNSResponder to activate daapd: that's incorrect.
> 	It needs to be mDNSPublish. Also the syntax specified is wrong for my version.

I'm afraid you misunderstood my intentions. I could rephrase the 
pkg-message to be more clear:

--cut--
To advertise the daapd service via ZeroConf/Rendezvous on your local
network, you've got two options:

1) if you selected the HOWL build option (or set WITH_HOWL), daapd
contains code to register its services with the howl daemon
(mDNSResponder).

2) otherwise, you can install the net/mDNSResponder port, and use
that with a command line like:

   mDNSResponderPosix -p 3689 -t _daap._tcp. -n `hostname`
--cut--

Would this be clearer?

/Lars
Comment 4 Lars Thegler 2004-07-02 23:09:59 UTC
paul beard wrote:
>  Also, it appears daapd is linked against the wrong libhttpd or perhaps 

daapd is statically linked to the library installed by the 
www/libhttpd-persistent port. This was updated to version 1.3h on 
23-June. Upgrade that port, and rebuild daapd.

/Lars
Comment 5 paul beard 2004-07-02 23:11:31 UTC
On Jul 2, 2004, at 3:04 PM, Lars Thegler wrote:

>   mDNSResponderPosix -p 3689 -t _daap._tcp. -n `hostname`
>

Well, I don't get "mDNSResponderPosix" when I build and install this.

[/opt/ports/audio/daapd]# which mDNSResponderPosix
(root@red.paulbeard.org)-(03:07 PM / Fri Jul 02)
[/opt/ports/audio/daapd]# locate mDNSResponderPosix
(root@red.paulbeard.org)-(03:07 PM / Fri Jul 02)
[/opt/ports/audio/daapd]#

And *Responder doesn't publish: *Publish does. the only arguments that 
*Responder takes are these:
-h              this help
-v              display version
-d              run in debug mode
-i ifname       run only on interface ifname
-a addr         run only on interface whose address is addr
-f config_file  load config_file

So I'm able to get mDNSResponder and mDNSPublish to work just fine, but 
getting daapd to work is a whole 'nother thing.


--
Paul Beard
<www.paulbeard.org/>
paulbeard [at] mac.com
Comment 6 paul beard 2004-07-02 23:11:37 UTC
On Jul 2, 2004, at 3:09 PM, Lars Thegler wrote:

> daapd is statically linked to the library installed by the 
> www/libhttpd-persistent port. This was updated to version 1.3h on 
> 23-June. Upgrade that port, and rebuild daapd.
>

I've done that couple of times: shouldn't ldd show that?

ldd /usr/local/sbin/daapd
/usr/local/sbin/daapd:
         libid3tag.so.2 => /usr/local/lib/libid3tag.so.2 (0x28091000)
         libz.so.2 => /usr/lib/libz.so.2 (0x280a1000)
         libhowl-0.9.4.so.0 => /usr/local/lib/libhowl-0.9.4.so.0 
(0x280ae000)
         libmp4v2.so.0 => /usr/local/lib/libmp4v2.so.0 (0x28178000)
         libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x282a9000)
         libm.so.2 => /usr/lib/libm.so.2 (0x282ee000)
         libc_r.so.4 => /usr/lib/libc_r.so.4 (0x28309000)
         libc.so.4 => /usr/lib/libc.so.4 (0x283bf000)
         libgnugetopt.so.1 => /usr/local/lib/libgnugetopt.so.1 
(0x28458000)

--
Paul Beard
<www.paulbeard.org/>
paulbeard [at] mac.com
Comment 7 paul beard 2004-07-03 00:33:17 UTC
On Jul 2, 2004, at 3:09 PM, Lars Thegler wrote:

> daapd is statically linked to the library installed by the 
> www/libhttpd-persistent port. This was updated to version 1.3h on 
> 23-June. Upgrade that port, and rebuild daapd.
>

OK, it works now. I'm not getting something about how it all works with 
the various flavors mDNSResponder. I made daapd w/o Howl and it all 
seems to work fine with my existing mDNSPublish infrastructure.

Thanks.
--
Paul Beard
<www.paulbeard.org/>
paulbeard [at] mac.com
Comment 8 Lars Thegler freebsd_committer freebsd_triage 2004-07-03 15:29:16 UTC
State Changed
From-To: open->feedback

Asked for clarification on pkg-message wording.
Comment 9 paul beard 2004-07-06 23:01:34 UTC
Now that I understand better the relationship capabilities of the 
different mDNS ports, I'm submitting this diff: I don't know if it will 
help anyone else (Lars said mine was the first feedback he had gotten). 
The crux of this seems to be whether or not the user already has some 
mDNS-based services running and what daapd needs.

--- pkg-message.new     Tue Jul  6 14:56:38 2004
+++ pkg-message Tue Jul  6 14:52:48 2004
@@ -28,12 +28,11 @@

    %%LOGDIR%%/daapd.log

-To advertise the server and you have net/howl installed and running,
-use this:
+To advertise the server, you can either use howl, or run 
net/mDNSResponder
+with a command line like:

-       mDNSPublish `browseable name` _daap._tcp 3689 &
+  mDNSResponderPosix -p 3689 -t _daap._tcp. -n `hostname`

-Or you can run net/mDNSResponder with a command line like:
-
-       mDNSResponderPosix -p 3689 -t _daap._tcp. -n `browseable name`
+Enjoy!

--
Paul Beard
<www.paulbeard.org/>
paulbeard [at] mac.com
Comment 10 Lars Thegler 2004-07-10 10:41:26 UTC
paul beard wrote:
>  -       mDNSPublish `browseable name` _daap._tcp 3689 &

No. As I wrote in a previous mail, you are not supposed to use 
mDNSPublish, it is just a sample application, whose only purpose is to 
take the command line arguments, and call sw_discovery_publish(). Daapd 
does this already, if compiled with the WITH_HOWL option - see daapd.cc, 
line 996.

I'll close the PR now - I've clarified the pkg-message as best I can. If 
you still have problems getting the daapd+howl combo to run properly, 
let's take it from there.

/Lars

PS. You've got your diffs the wrong way around.
Comment 11 Lars Thegler freebsd_committer freebsd_triage 2004-07-10 10:44:46 UTC
State Changed
From-To: feedback->closed

pkg-message clarified.