mirror of
https://github.com/vdr-projects/vdr.git
synced 2025-03-01 10:50:46 +00:00
Auto-Update wiki pages
AutoMirror Bot
parent
254e90b665
commit
2a3f5c7213
@ -196,8 +196,7 @@
|
||||
<section>
|
||||
<h1>SIGNALS</h1>
|
||||
<dl>
|
||||
<dt><h3>SIGINT,
|
||||
SIGTERM</h3></dt>
|
||||
<dt><h3>SIGINT, SIGTERM</h3></dt>
|
||||
<dd>Program exits with status 0.</dd>
|
||||
<dt><h3>SIGHUP</h3></dt>
|
||||
<dd>Program exits with status 1. This can be used to force a reload, for
|
||||
@ -205,8 +204,7 @@
|
||||
</dl>
|
||||
</section>
|
||||
<section>
|
||||
<h1>EXIT
|
||||
STATUS</h1>
|
||||
<h1>EXIT STATUS</h1>
|
||||
<dl>
|
||||
<dt><h3>0</h3></dt>
|
||||
<dd>Successful program execution.</dd>
|
||||
@ -263,8 +261,7 @@
|
||||
</dl>
|
||||
</section>
|
||||
<section>
|
||||
<h1>SEE
|
||||
ALSO</h1>
|
||||
<h1>SEE ALSO</h1>
|
||||
<p><a href="VDR-file-formats-and-conventions">vdr(5)</a>,<a href="svdrpsend-command-reference">svdrpsend(1)</a></p>
|
||||
</section>
|
||||
<section>
|
||||
@ -273,8 +270,7 @@
|
||||
See the file <i>CONTRIBUTORS</i> in the <b>vdr</b> source distribution.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h1>REPORTING
|
||||
BUGS</h1>
|
||||
<h1>REPORTING BUGS</h1>
|
||||
<p>Report bugs to <vdr-bugs@tvdr.de>.</p>
|
||||
</section>
|
||||
<section>
|
||||
|
||||
@ -303,8 +303,7 @@
|
||||
<p><b>...:201;2001=deu,2002=eng:...</b></p>
|
||||
<p></p>
|
||||
</dd>
|
||||
<dt><h3>Conditional
|
||||
access</h3></dt>
|
||||
<dt><h3>Conditional access</h3></dt>
|
||||
<dd>A hexadecimal integer defining how this channel can be accessed:
|
||||
<table>
|
||||
<tr>
|
||||
@ -536,8 +535,7 @@
|
||||
</tr>
|
||||
</table>
|
||||
</dd>
|
||||
<dt><h3>Auxiliary
|
||||
data</h3></dt>
|
||||
<dt><h3>Auxiliary data</h3></dt>
|
||||
<dd>An arbitrary string that can be used by external applications to store any
|
||||
kind of data related to this timer. The string must not contain any
|
||||
newline characters. If this field is not empty, its contents will be
|
||||
@ -658,8 +656,7 @@ There can be any number of actions in a line, including none at all - in which
|
||||
the file. Devices may be listed more than once.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>SATELLITE
|
||||
CHANNEL ROUTING (SCR)</h2>
|
||||
<h2>SATELLITE CHANNEL ROUTING (SCR)</h2>
|
||||
<p>The file <i>scr.conf</i> contains the channel definitions of the
|
||||
SCR device in use. The format is</p>
|
||||
<p>channel frequency [pin]</p>
|
||||
@ -690,8 +687,7 @@ There can be any number of actions in a line, including none at all - in which
|
||||
listed more than once, only its first appearance counts.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>REMOTE
|
||||
CONTROL KEYS</h2>
|
||||
<h2>REMOTE CONTROL KEYS</h2>
|
||||
<p>The file <i>remote.conf</i> contains the key assignments for all
|
||||
remote control units. Each line consists of one key assignment in the
|
||||
following format:</p>
|
||||
@ -703,8 +699,7 @@ There can be any number of actions in a line, including none at all - in which
|
||||
control delivers when the given key is pressed.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>KEY
|
||||
MACROS</h2>
|
||||
<h2>KEY MACROS</h2>
|
||||
<p>The file <i>keymacros.conf</i> contains user defined macros that
|
||||
will be executed whenever the given key is pressed. The format is</p>
|
||||
<p><b>macrokey [@plugin] key1 key2 key3...</b></p>
|
||||
@ -832,8 +827,7 @@ Calendar: date;echo;cal
|
||||
the user whether this command shall really be executed.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>RECORDING
|
||||
COMMANDS</h2>
|
||||
<h2>RECORDING COMMANDS</h2>
|
||||
<p>The file <i>reccmds.conf</i> can be used to define commands that
|
||||
can be applied to the currently highlighted recording in the
|
||||
"Recordings" menu. The syntax is exactly the same as described for
|
||||
@ -842,8 +836,7 @@ Calendar: date;echo;cal
|
||||
blank and enclosed in single quotes.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>SVDRP
|
||||
HOSTS</h2>
|
||||
<h2>SVDRP HOSTS</h2>
|
||||
<p>The file <i>svdrphosts.conf</i> contains the IP numbers of all
|
||||
hosts that are allowed to access the SVDRP port. Each line contains one IP
|
||||
number in the format</p>
|
||||
@ -912,8 +905,7 @@ Calendar: date;echo;cal
|
||||
will be used.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>AUDIO/VIDEO
|
||||
DATA</h2>
|
||||
<h2>AUDIO/VIDEO DATA</h2>
|
||||
<p>The files <i>00001.ts</i>...<i>65535.ts</i> are the actual
|
||||
recorded data files. In order to keep the size of an individual file below a
|
||||
given limit, a recording may be split into several files. The contents of
|
||||
@ -1007,8 +999,7 @@ Calendar: date;echo;cal
|
||||
<p>- the comment is currently not used by VDR</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>SORT
|
||||
MODE</h2>
|
||||
<h2>SORT MODE</h2>
|
||||
<p>The file <i>.sort</i> (if present in a directory) contains an
|
||||
integer number defining the mode by which this directory shall be sorted
|
||||
when presented in a menu.</p>
|
||||
@ -1025,8 +1016,7 @@ Calendar: date;echo;cal
|
||||
</table>
|
||||
</section>
|
||||
<section>
|
||||
<h2>RECORDING
|
||||
TIMER</h2>
|
||||
<h2>RECORDING TIMER</h2>
|
||||
<p>The file <i>.timer</i> (if present in a recording directory)
|
||||
contains the full id of the timer that is currently recording into this
|
||||
directory. Timer ids are of the form</p>
|
||||
@ -1036,8 +1026,7 @@ Calendar: date;echo;cal
|
||||
and is deleted when it ends.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>EPG
|
||||
DATA</h2>
|
||||
<h2>EPG DATA</h2>
|
||||
<p>The file <i>epg.data</i> contains the EPG data in an easily
|
||||
parsable format. The first character of each line defines what kind of data
|
||||
this line contains.</p>
|
||||
@ -1200,8 +1189,7 @@ Calendar: date;echo;cal
|
||||
into the <i>info</i> file of a recording that is made for such an event.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>CAM
|
||||
DATA</h2>
|
||||
<h2>CAM DATA</h2>
|
||||
<p>The file <i>cam.data</i> contains information about which CAM in
|
||||
the system can decrypt a particular channel. Each line in this file contains
|
||||
a channel id, followed by one or more (blank separated) numbers, indicating
|
||||
@ -1216,8 +1204,7 @@ Calendar: date;echo;cal
|
||||
program ends. If the file is read-only, it will not be overwritten.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>CAM
|
||||
AUTO RESPONSE</h2>
|
||||
<h2>CAM AUTO RESPONSE</h2>
|
||||
<p>If your CAM keeps popping up annoying messages or you want to make
|
||||
sure VDR can record programmes with parental rating without having to enter
|
||||
the PIN (in case you can't turn that off in your CAM), you can set up auto
|
||||
@ -1274,8 +1261,7 @@ Calendar: date;echo;cal
|
||||
to be comment.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h2>COMMANDLINE
|
||||
OPTIONS</h2>
|
||||
<h2>COMMANDLINE OPTIONS</h2>
|
||||
<p>If started without any options, vdr tries to read any files in the
|
||||
directory /etc/vdr/conf.d with names that do not begin with a '.' and that
|
||||
end with '.conf'. These files are read in alphabetical order. The format of
|
||||
@ -1301,8 +1287,7 @@ Calendar: date;echo;cal
|
||||
</section>
|
||||
</section>
|
||||
<section>
|
||||
<h1>SEE
|
||||
ALSO</h1>
|
||||
<h1>SEE ALSO</h1>
|
||||
<p><a href="VDR-command-reference">vdr(1)</a></p>
|
||||
</section>
|
||||
<section>
|
||||
@ -1310,8 +1295,7 @@ Calendar: date;echo;cal
|
||||
<p>Written by Klaus Schmidinger.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h1>REPORTING
|
||||
BUGS</h1>
|
||||
<h1>REPORTING BUGS</h1>
|
||||
<p>Report bugs to <vdr-bugs@tvdr.de>.</p>
|
||||
</section>
|
||||
<section>
|
||||
|
||||
@ -41,8 +41,7 @@
|
||||
License can be found in /usr/share/common-licenses/GPL.</p>
|
||||
</section>
|
||||
<section>
|
||||
<h1>SEE
|
||||
ALSO</h1>
|
||||
<h1>SEE ALSO</h1>
|
||||
<p><a href="VDR-command-reference">vdr(1)</a>, <a href="VDR-file-formats-and-conventions">vdr(5)</a></p>
|
||||
</section>
|
||||
</div>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user