One way to go around this without using network access is to edit daemon.conf and client.conf (usually in /etc/pulse) and have them use a pulse-cookie file. The way I did it before was to get that file saved as /etc/pulse-cookie, set it g+w for 'pulse-access' group, for example, and add 'mpd' and your own user in that group.
More information about this can be found in the man pages for 'pulse-client.conf' and 'pulse-daemon.conf' Hope this can help... Jason ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team