Bug #546
closed
patch to use the right svdrpport 6419, up from vdr-1.7.15
Added by Anonymous almost 14 years ago.
Updated almost 14 years ago.
Description
I don't get an OSDmessage with vdr-1.7.16
attached diff is a possible fix to use the right svdrpport, up from vdr-1.7.15
Cheers
(realname on top in the .diff)
Files
- Assignee set to Joe_D
- % Done changed from 0 to 80
Why don't you just add an entry into your services file (svdrp/tcp)?
- Status changed from New to Rejected
No answer till now -> Rejected
services file?
where is the information for this?
how is the syntax of this?
anyway,
Port 2001 and Port 6419 are the default ports used by VDR
this to handle or to fix on install should not be at least by the user himself
only in the case he will not use the default ports, he should change it by himself in the "services file???"
make it more clear for the user how is it to handle
and/or better,
make it more comfortable with this fix...
- Target version changed from 0.0.9 to 0.1.0
- % Done changed from 80 to 100
"services file?
where is the information for this?
how is the syntax of this?"
svdrp is now an "official" service on port 6419 and you should have an entry in /etc/services like this:
svdrp 6419/tcp # VDR
"make it more clear for the user how is it to handle
and/or better,
make it more comfortable with this fix..."
Sorry for this. Your patch it binding markad standalone-version to the VDR sources, and i dont want this.
I'll add the above into the README, ok?
Sorry for this. Your patch it binding markad standalone-version to the VDR sources, and i dont want this.
I understand, this is the reason ...
I'll add the above into the README, ok?
you can do this at first,
anyway, i think in the future the registred svdrp service will added per default in the /etc/services on the diffrent Distris,...
thanks for your time and work for now :)
Also available in: Atom
PDF