2010-05-07 08:13:42     mpd: "problems setsid'ing"

Document created by Aaronwu Employee on Aug 21, 2013
Version 1Show Document
  • View in full screen mode

2010-05-07 08:13:42     mpd: "problems setsid'ing"

Rob Maris (GERMANY)

Message: 89216   

 

I'm trying to get mpd up and running using current SVN trunk sources. 4 Source files (V0.13.2) are vfork-patched according to mpd-0.13.2-fork.patch. In one of these files, main.c, an alternative to vfork, a call to daemon() is used. I'm not sure whether this alternative call makes problems or anything erroneous is originated in the setsid() call.

 

The problems arises upon invocation of mpd: "problems setsid'ing".

 

- Rob

 

 

 

Note: I have also experimented with V 0.15.9, which should provide a broader support of audio formats. In this version a fork() call is performed at one central place in daemon.c.

QuoteReplyEditDelete

 

 

2010-05-07 22:43:33     Re: mpd: "problems setsid'ing"

Mike Frysinger (UNITED STATES)

Message: 89246   

 

svn up and try again

 

QuoteReplyEditDelete

 

 

2010-05-10 05:42:36     Re: mpd: "problems setsid'ing"

Rob Maris (GERMANY)

Message: 89279   

 

OK, mpd now works well as daemon,

 

however, just as a music stream is opened, nothing is audible, several things tried, also local mp3 file and modifications in mpd.conf. Upon opening a stream, the listening socket is closed.

 

Alternatively, mp3play operates correct.

 

Perhaps anybody is able to verify the operation. For the sake of completeness a CLI transcript is given below.

 

root: /> mpd --no-daemon --verbose --stdout

binding to any address

flushing warning messages

done flushing warning messages

current locale is "C"

setting filesystem charset to ISO-8859-1

setFsCharset: fs charset is: ISO-8859-1

reading DB

No "audio_output" defined in config file

Attempt to detect audio output device

Attempting to detect a alsa audio device

Successfully detected a alsa audio device

mixer control "PCM" not usable at line 63

using software volume

interface 0: opened from 127.0.0.1

interface 0: process command "status"

interface 0: command returned 0

interface 0: process command "playlistinfo "-1""

interface 0: command returned 0

interface 0: closed

interface 0: opened from 127.0.0.1

interface 0: process command "listall """

interface 0: command returned 0

interface 0: process command list

processListOfCommands: process command "add "  sc8.1.fm:6950""

add to playlist:   sc8.1.fm:6950

get song:   sc8.1.fm:6950

processListOfCommands: command returned 0

interface 0: process command list returned 0

interface 0: closed

interface 0: opened from 127.0.0.1

interface 0: process command "status"

interface 0: command returned 0

interface 0: process command "play "0""

playlist: play 0:"  sc8.1.fm:6950"

closeAllListenSockets called

closing listen socket 0

interface 0: closed

took 0.000000 to init player

copyMpdTagToOB: !acceptMetadata || !tag

../../mpd-0.13.2/src/inputStream_http.c: Port: 6950

inputStream_http: metaName: 1.FM - Back To The 80s

inputStream_http: metaTitle: 80s 24 Hours A Day! -

inputStream_http: metaTitle: J. GEILS BAND - I MUST HAVE GOT LOST LIVE

 

.

QuoteReplyEditDelete

 

 

2010-05-10 07:32:05     Re: mpd: "problems setsid'ing"

Rob Maris (GERMANY)

Message: 89282   

 

Side notice:

 

Since I'm comparing the exact behaviour with mpd on a Ubuntu Linux machine, while using a gmpc frontend, I'm going to upgrade V0.13.2 to V0.14.2. I'm struggling about how to prepare a proper build-mpd-0.14.2 directory. ./configure yields errors. I'd appreciate to get a pointer to appropriate how-to information.

 

- Rob

QuoteReplyEditDelete

 

 

2010-05-10 11:20:37     Re: mpd: "problems setsid'ing"

Mike Frysinger (UNITED STATES)

Message: 89286    mpd hasnt been upgraded past 0.13.x because newer versions rely on

glib which stupidly requires i18n support

Attachments

    Outcomes