06-24-2024, 06:50 PM
Turning off the mount monitor had no effect. Verbose mpd logging showed that the apparently frozen state isn't actually frozen though, there are, very slowly, log entries, looping through this sort of thing:
Any clue what that means?
Code:
un 24 19:46 : client: [225] process command "close"
Jun 24 19:46 : client: [225] command returned 4
Jun 24 19:46 : client: [225] closed
Jun 24 19:47 : client: [226] opened from 127.0.0.1:36500
Jun 24 19:47 : client: [226] process command "status"
Jun 24 19:47 : client: [226] command returned 0
Jun 24 19:47 : client: [226] process command "stats"
Jun 24 19:47 : client: [226] command returned 0
Jun 24 19:47 : client: [226] process command "close"
Jun 24 19:47 : client: [226] command returned 4
Jun 24 19:47 : client: [226] closed
Jun 24 19:47 : client: [227] opened from 127.0.0.1:55048
Jun 24 19:47 : client: [227] process command "status"
Jun 24 19:47 : client: [227] command returned 0
Jun 24 19:47 : client: [227] process command "stats"
Jun 24 19:47 : client: [227] command returned 0
Jun 24 19:47 : client: [227] process command "close"
Jun 24 19:47 : client: [227] command returned 4
Jun 24 19:47 : client: [227] closed
Any clue what that means?
----------------
Robert
Robert