Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] Re: 18 Minutes - what does that tell?
vdr-bounce@linuxtv.org wrote on 03.04.2002 17:05:45:
[ lines removed ]
> So this doesn't seem to be the reason.
>
> Another problem I had with nofushd was that it tried to store the data
> in (virtual) memory (OK, thats what it is supposed to do :-)) and then
> tried to flush a huge amount of data to the disk. Of course the disk
> was sleeping. During the spinup and flush data, often it looked like
> buffers would overflow resulting in dropouts.
> It seems that noflushd could not receive new data (from vdr) while
> flushing old ones - or at least not fast enough.
> Had anybody a similar problem or is somebody successfully driving a
> vdr box with noflushd?
> Maybe it's a good idea to stop noflushd on start of a recording and
> start it again when all recordings are finished?
That's what I do with my --record script that I pass to vdr as a
parameter. Works fine.
#!/bin/sh
case "$1" in
before)
echo "Before recording $2"
/etc/init.d/noflushd stop
;;
after)
echo "After recording $2"
/etc/init.d/noflushd start
;;
edited)
echo "Edited recording $2"
;;
*)
echo "ERROR: unknown state: $1"
;;
esac
>
> Richard
>
>
>
Home |
Main Index |
Thread Index