Difference between revisions of "Talk:Music Player Daemon"

From ArchWiki
Jump to: navigation, search
Line 20: Line 20:
  
 
So I guess you're saying that the answer is: "because it's a daemon." That suffices, thanks. [[User:Mollison|Mollison]] 01:12, 16 August 2009 (EDT)
 
So I guess you're saying that the answer is: "because it's a daemon." That suffices, thanks. [[User:Mollison|Mollison]] 01:12, 16 August 2009 (EDT)
 +
 +
 +
I'm going to resurrect this because, based on my recent install (and from comments in many of the posts on the forums) I think it makes far more sense to detail two '''clear''' options:
 +
 +
:: 1. Install for single user use (all files in ~/.mpd) - flagged 'recommended'
 +
 +
:: 2. Install for multi-user use (files in {/etc,/var,/lib})
 +
 +
For the single user, it is just as simple to start mpd from .xinitrc and it means you don't have issues with permissions etc...
 +
 +
Thoughts?
 +
 +
[[User:Jasonwryan|Jasonwryan]] 01:34, 7 December 2009 (EST)

Revision as of 06:34, 7 December 2009

I think this article needs to be reworked. Right now it's just single user with weird permissions (which did not work for me.) This needs to be more generalized for multiple users so it can be done properly. I'll look into it and consider some major modifications. --Statix 01:01, 5 October 2008 (EDT)


Still planning to?--stefanwilkens 20:31, 5 March 2009 (EST)


Because MPD is running as another user, it takes full control over the sound device and any other programs starting up as my user cannot open the sound device, i received the error Error opening ALSA device "hw:0,0": Device or resource busy. This differs slightly from the error in the article. As seen here http://mpd.wikia.com/wiki/Configuration the two lines here ipc_key_add_uid and falseipc_perm 0666 in /etc/asound.conf resolved the issue which allowed more than one user to read the sound device. This may help someone although its more of an issue with dmix than mpd but i only discovered it due to dmix running as a different user.

--Tama00 08:42, 22 June 2009 (EDT)


I do not understand why installing with MPD running as root initially and then switching over to user 'mpd', is given as the preferred method. I'd like to see an explanation in the page of why this is preferred ,as opposed to installing MPD just like any other program (e.g. putting the config in your normal ~, etc.). For me, the second way seemed more logical and easier.

Mollison 02:52, 15 August 2009 (EDT)

I think it's quite clearly described that you need it to be able to autostart from your rc.d directory. Wuncidunci

So I guess you're saying that the answer is: "because it's a daemon." That suffices, thanks. Mollison 01:12, 16 August 2009 (EDT)


I'm going to resurrect this because, based on my recent install (and from comments in many of the posts on the forums) I think it makes far more sense to detail two clear options:

1. Install for single user use (all files in ~/.mpd) - flagged 'recommended'
2. Install for multi-user use (files in {/etc,/var,/lib})

For the single user, it is just as simple to start mpd from .xinitrc and it means you don't have issues with permissions etc...

Thoughts?

Jasonwryan 01:34, 7 December 2009 (EST)