Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] AW: Re: AW: Re: AW: VDR shutdown problem
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.
So short, Martin
Home |
Main Index |
Thread Index