[vdr] AW: Re: VDR shutdown problem

["Martin Geistreiter" <martin.geistreiter@gmx.net>]

>
> MG>
> MG> >if that's the case, you should
> MG> > 1. ensure that your hardware clock is running correct time
> MG> > 2. choose one transponder, which you trust about time and set it
> MG> >    soemwhere in the setup
> MG>
> MG> >btw.:  use  -l  option, if you want nvram-wakeup to redirect all
> output
> MG> >to /var/log/messages
> MG>
> MG>
> MG> A possible solution fort this to insert the following line in the
> MG> Vdrshutdown script before the shutdown command:
>
> >better,  somewhere  inside  your  shutdown  scripts,  like  on SuSE,
> IIRC,
> >/etc/sbin.d/halt
>
> in the suse script  halt  there alredy is a hwclock command, but it
does
> not work form e; dont know why...
> while shutdown it says "setting hwclock to system time   done" but if
I
> look in the cmos its still wrong; upper described solution works fo
me.
>
>
> MG>
> MG> hwclock --systohc
>
> >And  you  should  choose  a  "trustable"  transponder anyway, because
> some
> >transponders  send  their  local  time  and some send (or at least
used
> to
> >send) just crap
>
> yep; thanx forgot to write that i use ARD as my time source.
>


>.. but that does not help if your box only starts to record something
on
>another transponder. So I do this always in my runvdr script before I
start
>VDR:


>SETUPCF=/usr/local/src/VDRtmp/setup.conf
>sed -e /CurrentChannel/d $SETUPCF > $SETUPCF.tmp
>mv $SETUPCF.tmp $SETUPCF
>echo "CurrentChannel = 1" >> $SETUPCF

>"1" is ARD in my case.
>So it realy starts on ARD. After some minutes it gets the timer and
>switches
>than to the right channel. The time is enough to adjust the system
time. >The
>rest is like above.

>Kind regards
>Manfred

yep, Manfred thats a good idea; will insert it into my system at once;
btw wouldn't it be better to connect to VDR via SVDR and switch to "ARD"
?!?
just a thought..

Martin