Closed jlp2 closed 4 years ago
This is a known problem but so far it didn't bother me as I've just disabled vdrpbd on my HTPC. Kodi doesn't need it anyway. Again: vdrpbd is a separate project which is maintained here:
https://projects.vdr-developer.org/projects/vdrpbd
To fix this I have to rework the help message generation. I already did this for repo-make and just have to port the fix back to vdrpbd as soon as I find the time.
This is a known problem but so far it didn't bother me as I've just disabled vdrpbd on my HTPC. Kodi doesn't need it anyway.
I see what you mean. Unfortunately I use separate Kodi-Boxes (Intel NUC) and an extra server with vdr. The vdr regulates the power management on this server and so that you don't accidentally switch it off when recordings are still running, vdrpd was an excellent fit.
To fix this I have to rework the help message generation. I already did this for repo-make and just have to port the fix back to vdrpbd as soon as I find the time.
Thats would be great. Thank you for your effort!
I already did this for repo-make...
I found your rework for the message generation in repo-make and tried to fix the vdrpbd file in the same manner.
@@ -16,7 +16,7 @@
# along with this program. If not, see <http://www.gnu.org/licenses/>.
use strict;
-use Pod::Simple::Text;
+use Pod::PlainText;
use Getopt::Std;
use POSIX;
use threads;
@@ -152,7 +152,7 @@
sub HELP_MESSAGE {
# Print out the built-in POD documentation in case of --help parameter
- Pod::Simple::Text->filter($0);
+ Pod::PlainText->new(sentence => 0)->parse_from_file($0);
}
sub ParseConfig {
I don't really have any idea what I was doing, but vdrpbd started and worked after that. Unfortunately I don't know how to submit patches to https://projects.vdr-developer.org/projects/vdrpbd, so I'll post it here now.
Future issues about vdrpbd can be reported here:
https://github.com/M-Reimer/vdrpbd/issues
I've also disabled the issue tracker on projects.vdr-developer.org as it is more convenient to have all my issues tracked at the same hosting platform.
vdrpbd gibt nach dem starten durch systemd, aber auch manuell via "vdrpbd -f" folgende Fehlermeldung aus: