Isnt the whole idea of having shepherd update itself supposed to solve this sort of problem? Just have to wait until the issue is addressed by the shepherd devs and it will start automatically working again.

Yes Greg, but as I'm sure you will recall, Shepherd totally failed recently for a two week period, and for no apparent reason: There was no EPG at all for a few days and I find this unacceptable.
You are correct in that the whole idea of Shepherd is for it to work, but with it there are *two* sources of error: 1. The package might break, and you have no control over it or 2. Oztivo might change something randomly and without reason, and fail to tell us.
The only thing that will cause my script to fail is the latter.

Shepherd is a lot less clear than a simple Perl script, and you have no control over whether or not it updates itself, for better or worse.

Belt and braces is what we need, or if you like, alternatives.

regards

Mike

_________________
*********************
LinHES 7.4
Australian Dragon
*********************

I saw all of those posts, but it worked flawlessly here in Adelaide. I wonder why the difference.

Fine also in Perth, but maybe the 7 days in advance thing covered any downtime windows?

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector

Since changing the symlink and then manually reconfiguring Shepherd I have had no issues what so ever. This then cames back to a personal preference whether you just want to change the symlink or go Mike's way.

_________________
Girkers

My shepherd was working fine...I had some router issues and lost internet for a week.
Now mythfilldatabase displays the following and no content is being updated?

*******
WARNING: Shepherd is being run too frequently!!
Please don't run Shepherd so frequently.
Re-using (existing cached) output for this run.
*******

Any ideas?

Hi Dave,

A bit late reply, but incase you are still listening...

I'd look at running it along the lines of the shepherd website (they recommend using crontab instead of symlinking the grabbers). I did this myself in R5.5 when i upgraded last night, seems to work ok so far.

Cheers,

Nathan

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector

Hey guys i installed the new knopp 5.5 and saw TV_Grab_au_mike (oztivo) as a XMLTV option. So i used it, signed up to oztivo and configured the grabber. Didn't work, i just downloaded the new update in the last post mike suggested. Tried it , same thing.

comes up with
Failed to download data for SevenHD
Failed: xmltv returned error code 256

It does that for all channels , what should i be checking to get it to work?

You were meant to install with "country=au" or "ausdragon2" to run my script. It won't work properly unless you do that. tv_grab_au is meant to be a symlink to /usr/bin/tv_grab_au_mike

You could run the script manually, but I haven't ever done that. It's /usr/bin/AusDragonTweaker.sh. Think there may be things in Knoppmyth-run that assist it, too.

Used correctly, it's really, really easy to set up.

Mike

_________________
*********************
LinHES 7.4
Australian Dragon
*********************

As a point of reference, I went down the path of Shepherd and symlinked tv_grab_au to shepherd and have not had any problems.

_________________
Girkers

I've just noticed tonight (In Perth) that it's out by 1 hour... I think shepherd is getting it's timezone from over east? Any ideas?

Bj

_________________
Backend/Front : Core2 1.86Ghz 1GBRAM 500GB HDD 32" LCD
Frontend1:VIA M10K Diskless 17" LCD Kitchen
Frontend2:VIA M10K Diskless 22" LCD
Frontend3:Centrino in cubby

Hi Bj,

I've got shepherd running in Perth, and as far as i can tell the times are all correct. Several shows recorded yesterday, and they were over the correct time span. Although, i did see that there was only guide data for the next 4 days, so shepherd might not have run since friday?

What part is "it out by an hour"? Is it the whole guide? one channel?

I'll have a look at mine later to see if i'm having any problems like you describe, but it would seem that if you've only just started experiencing it, then the east coast daylight saving would sound to be the obvious thing to blame. Maybe the grabbers/guide sources all got confused? Might need to re-run mythfilldatabase?

Nath

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector

The Eastern States went to DST on Sunday. We don't switch till the end of the month. Any Foxtel channel will be a hour ahead till we switch.

It's odd, I have had a few mates ring me saying their mythboxes were out, and it seems the XML timezone offset (in the backend) needs to be set to +900 to fix it. I reran mythfilldatabase but it is still out if I don't use +900. It was on auto which worked before - it's only since over east got DST. This is for all the free to air channels in Perth. I don't have foxtel.

_________________
Backend/Front : Core2 1.86Ghz 1GBRAM 500GB HDD 32" LCD
Frontend1:VIA M10K Diskless 17" LCD Kitchen
Frontend2:VIA M10K Diskless 22" LCD
Frontend3:Centrino in cubby

man, that is a serious cubby...

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector