On Sunday 14 June 2009, Martin Gansser wrote:
> Hi,
>
> VDR 1.6.0 exited with status 134, when generating a iso-file with
> vdr-burn.
>
> system is Fedora 11 x86_64
Possibly a vdr-burn/boost compile/runtime mismatch.
https://bugzilla.redhat.com/show_bug.cgi?id=505893
__
Hi,
VDR 1.6.0 exited with status 134, when generating a iso-file with
vdr-burn.
system is Fedora 11 x86_64
installed rpm packages:
vdr-osdteletext-0.8.1-2.fc11.x86_64
vdr-burn-debuginfo-0.1.0-0.18.pre21.fc11.x86_64
vdr-1.6.0-21.fc11.x86_64
vdr-mp3-0.10.1-7.fc11.x86_64
vdr-devel-1.6.0-21.fc11.x86
On Monday 11 June 2007, Kartsa wrote:
> Ville Skyttä kirjoitti:
> >
> > If you wish to debug it further, uncomment
> > DAEMON_COREFILE_LIMIT=unlimited at end of /etc/sysconfig/vdr and watch if
> > core dumps start to appear in /tmp.
>
> I'll give it a try. Would -t switch be helpfull with shutdown?
Ville Skyttä kirjoitti:
> On Sunday 10 June 2007, Kartsa wrote:
>
>> I've got fedora with runvdr from fedora vdr package and it tries to
>> restart VDR if exit code is something else than 0, 2 or 137. Sometimes
>> the exit code is 137 but most of the time it is 134. This causes VDR to
>> restart
On Sunday 10 June 2007, Kartsa wrote:
> I've got fedora with runvdr from fedora vdr package and it tries to
> restart VDR if exit code is something else than 0, 2 or 137. Sometimes
> the exit code is 137 but most of the time it is 134. This causes VDR to
> restart (or runvdr makes VDR to restart)
Most of the time when VDR shuts the box down using vdrshutdown script
there is a line in the log
runvdr: VDR exited with status 134, attempting restart
I've got fedora with runvdr from fedora vdr package and it tries to
restart VDR if exit code is something else than 0, 2 or 137. Sometimes
the
