paneologist

ok. just tested a lot.

ran epgrefresh with fake recording.

made 51 concurrent recordings.

ran epgrefresh again.

no problems yet.

an end of recording looks like that in the logs now:

2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [TIMER] stop recording on tuner: G
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [eDVBServiceRecord] stop recording!
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [eFilePushThreadRecorder] read got interrupted by signal, stop: 0
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: message repeated 1087 times: [ [eFilePushThreadRecorder] read got interrupted by signal, stop: 0]
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [eFilePushThreadRecorder] stopping thread
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [eFilePush] SIGUSR1 received
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [eFilePushThreadRecorder] read got interrupted by signal, stop: 1
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [eDVBRecordFileThread] waiting for aio to complete
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [eDVBRecordFileThread] buffer usage histogram (40 buffers of 188 kB)
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [eDVBRecordFileThread]   1:     33
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [eDVBRecordFileThread]   2:     33
2023-08-23T14:15:00+02:00 stb1.swabian.net enigma2: [eFilePushThreadRecorder] THREAD STOP