On 15 Feb 2007 "VDR User" <[EMAIL PROTECTED]> wrote:
> I was watching something via the mplayer plugin. A recording timer was
> triggered which aborted the mplayer playback. Is this behavior
> intentional? If so, can the abort be disabled while still allowing the
> timer to function properly?
On 26 Jan 2007 Marco Skambraks <[EMAIL PROTECTED]> wrote:
> On Thu, 25 Jan 2007, Halim Sahin wrote:
>>
>> The plugin remembers the last played directory but does not check if the
>> dir is
>> available before loading it.
>>
>> A fix can be possible in LoadDir function
>
> I made a dirty hac
On 2/17/07, Stefan Huelswitt <[EMAIL PROTECTED]> wrote:
On 15 Feb 2007 "VDR User" <[EMAIL PROTECTED]> wrote:
> I was watching something via the mplayer plugin. A recording timer was
> triggered which aborted the mplayer playback. Is this behavior
> intentional? If so, can the abort be disabl
Hi,
On Fri, Feb 16, bastlir wrote:
> > vdr can record from senders on V polarisation like sat1, prosieben ...
> > even without reloading the driver.
> > vdr can not record from any sender on H polarisation like ard, zdf ...
> > even with reloading the driver it doesn't work.
> > This explains, th
Darren Salt wrote:
We re-define SIGHUP, so that it doesn't terminate VDR instantly, but
instead checks for activity. If user and vdr is inactive, act just like
sigterm, if there's some activity, ignore the signal.
An external script could then repeat sending the SIGHUP periodically until
termi
