On Mar/21, Helmut Grohne wrote: > Sorry for having overlooked this detail. [1] is the point where I issue > mpc del 0. As it seems hard to reproduce I ran it again with strace, to > give you some pointers of what happens. > [...] > Given that it requires a large playlist I downgraded the severity to > normal. I hope this helps for solving the issue.
I can't reproduce this at all, even with a 65000-entry playlist; my run with loglevel=2 ressembles this: ~ # mpdcron -n Trying to load module: stats Added module suffix stats -> stats.so Trying user configured path `/home/seb/.mpdcron/modules/stats.so' Trying system path `/usr/lib/mpdcron-0.3/modules/stats.so' Found stats -> `/usr/lib/mpdcron-0.3/modules/stats.so' [stats] Initializing [stats] Successful bind to /home/seb/.mpdcron/stats.socket Loaded module `/usr/lib/mpdcron-0.3/modules/stats.so' Connecting to `localhost' on port 6602 with timeout 0 Connected to Mpd server, running version 0.15.0 Sending idle command with mask 0x9b [stats] Resolved `localhost' to 127.0.0.1 [stats] Successful bind to 127.0.0.1:7702 Sending status & currentsong commands to Mpd server [stats] New song detected (XXX YYY ZZZ), id: 279, pos: 66 Setting environment variable MC_CALLS_PLAYER=1 Running hook: hooks/player home directory: /home/seb/.mpdcron Failed to execute hook player: Failed to execute child process "hooks/player" (No such file or directory) Sending idle command with mask 0x9b Sending status & currentsong commands to Mpd server [stats] Saving old song (XXX YYY ZZZ), id: 279, pos: 66 Running "mpc del 0" doesn't change that behavior whatsoever: it doesn't look like mpdcron is asking the content of the playlist to mpd at all, but instead it's just concerned with the status+currentsong, which is what I would expect (not sure why it'd be trying to get the playlist content). Could you please post your mpdcron.conf, as I suspect there is some meaningful difference between our respective setups ? Cheers, --Seb -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
