hi to all
i was looking at /hdd/epg.dat file, but:
if already written and saved to hdd, who or when or why removes it before shutdown or before start? why not same for the file (epgcache) moved to usb?
thanks in advance
hi to all
i was looking at /hdd/epg.dat file, but:
if already written and saved to hdd, who or when or why removes it before shutdown or before start? why not same for the file (epgcache) moved to usb?
thanks in advance
epg.dat on /hdd is deleted on boot because you have rm -f /hdd/epg.* in rcS. the file on usb may not be deleted because the rcS has not been changed.
thanks for the answer...... why delete this files?
if you delete the lines in rcS, the files are deleted the same, no way to save it on hdd?
epgcache.cpp reading.... ehm not so easy.
epg.dat on /hdd should only be removed if you do a flash-erase
or if you boot a new installed image for the first time
see in rcS:
# check if /var/.init exist .. then no flash erase is needed .. this is new !
if [ ! -e /var/.init ]; then
# new /var/.init not found.. check if old /var/tmp/init exist..
# then not flash erase ist needed
if [ -e /var/tmp/init ]; then
# ok old /var/tmp/init exist.. no create the new flash_erase detection file..
touch /var/.init
# delete /var/tmp folder now..
rm -rf /var/tmp
# create link to /tmp <- this is mounted to RAM
ln -sf /tmp /var/tmp
else
# flash erase is needed ...
init=1
fi
fi
.
.
.
.
if [ $init -eq 1 ] ; then
rm /hdd/epg.*
fi
Alles anzeigen
dbluelle
ZitatOriginally posted by dbluelle
epg.dat on /hdd should only be removed if you do a flash-erase
or if you boot a new installed image for the first time
see in rcS:CodeAlles anzeigen# check if /var/.init exist .. then no flash erase is needed .. this is new ! if [ ! -e /var/.init ]; then # new /var/.init not found.. check if old /var/tmp/init exist.. # then not flash erase ist needed if [ -e /var/tmp/init ]; then # ok old /var/tmp/init exist.. no create the new flash_erase detection file.. touch /var/.init # delete /var/tmp folder now.. rm -rf /var/tmp # create link to /tmp <- this is mounted to RAM ln -sf /tmp /var/tmp else # flash erase is needed ... init=1 fi fi . . . . if [ $init -eq 1 ] ; then rm /hdd/epg.* fi
dbluelle
hi db, i know it, but......:
could i save the cache after epg.dat download? After shutdown (and restart), could enigma utilize that file, the complete epg (1,8mb), without having to stand everyrestart 3 minutes on epgchannel?
changing name of epg data file seems the only way to avoid hdd/epg.dat erasing.
comments?
I think I don't quite understand your problem
The epg.dat file is saved to hdd when going to deep standby and loaded when booting again.
As I said above, it is only erased if you do a flash-erase or if you install a new image.
So there's no need to download or upload it .
Maybe something's wrong with your installed image?
Which Dreambox model do you have?
(I can only tell you how this works on my DM7000, but AFAIK it should be the same on the 7020 and the 600)
dbluelle
ZitatAlles anzeigenOriginally posted by dbluelle
I think I don't quite understand your problem
The epg.dat file is saved to hdd when going to deep standby and loaded when booting again.
As I said above, it is only erased if you do a flash-erase or if you install a new image.
So there's no need to download or upload it .
Maybe something's wrong with your installed image?
Which Dreambox model do you have?
(I can only tell you how this works on my DM7000, but AFAIK it should be the same on the 7020 and the 600)
dbluelle
I never experienced what did you described as normal epg working. I noticed that because in this period was looking at the sources regarding epg. My 7000s ( year 2002 ?) 2b series, blue display, hdd maxtor 80g, does not work the same way. Perhaps my images are the problem, but I noticed that others too have the same behaviour, gemini360 for example, and the rcS file is quite the same as original one. I solved the problem as i described above, but i did not understand the reason why. Now if i put on hdd the old files too, these are deleted, not new ones, but the rcS contains the lines for removing of both types of files, old and new named..... and we are not in the init=1 condition.
Thanks dbluelle
ZitatOriginal von tension
Now if i put on hdd the old files too, these are deleted, not new ones, but the rcS contains the lines for removing of both types of files, old and new named..... and we are not in the init=1 condition.
I still don't understand it :(.
What do you mean by "old" and "new" files?
Do you have code for deleting /hdd/epg.dat in your rcS outside the init=1 condition ?
If that's the case then of course the file is deleted on every boot .
Perhaps you should ask the creators of your other images if they put some weird stuff into their images...
dbluelle
ZitatOriginal von tension
Now if i put on hdd the old files too, these are deleted, not new ones, but the rcS contains the lines for removing of both types of files, old and new named..... and we are not in the init=1 condition.
this for test we are not in condition init=1, and that the solution is renaming:
rcS:
hdparm -M 128 /dev/ide/host0/bus0/target${HD}/lun0/disc
if [ $init -eq 1 ] ; then
rm -f /hdd/epg.*
rm -f /hdd/xxx.*
fi
with 4 files on /hdd (epg.dat, epg.dat.md5, xxx.dat, xxx.dat.md5) and this rcS at boot
i find only xxx files. ok?
so on hdd:
epg.dat does not work, the files are deleted
xxx.epg.dat works, at boot we find the files on hdd, and the epg complete downloaded before restart is reloaded, all ok
rcS file is normal, standard, official.
if i change epgcache path like in webif, say put it to usb, the original files not renamed, are not deleted.
epg file on hdd does not work
epg file on usb works.
on my db, sky it epg. ok?
Hmm, very weird,
Maybe there are other scripts executed when booting ?
Otherwise I have no idea, sorry
dbluelle