Do you normally set it to "Auto"? Does date show the correct time? Does "echo $TZ" give Perth/Australia or something similar?

Mike

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

Now that you mention it, the date is correct.. I'm using R5B27

bj@MythTVServer:~$ date
Mon Oct 6 16:55:01 WST 2008

but this just returns a blank line

bj@MythTVServer:~$ echo $TZ

I just noticed tzconfig doesn't exist anymore... what do we use instead to set this after install?

_________________
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

Ah, ancient install. tzselect will be what you need. Australian time zones changed their roll forward/back dates this year. Debian patches were issued early this year, from memory (just after it was announced).

Regards

Mike

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

Ok I see. I can't upgrade to 5.5 because it just doesn't work on my diskless EPIA M10000 frontends... I gave up on that a long time ago during testing. It explains why you guys aren't having the same trouble then with the TZ Shepherd problem. Does anyone know what the patches where? Last time I patched this box for something it blew up?!

Otherwise if someone has got a diskless EPIA working on R5.5 I'd go with the new version and not bother with this ancient software

Cheers

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 encountered a similar (the same?) problem in reards to the time zone shift. Did tzselect resolve the issue for you?

Cheers

no but I haven't looked into it any further... I just changed the offset to +900 in the backend setup until I find out what patches I need. What tzselect is set to is correct, and the clock is correct, just the whole listings / recordings are out by an hour.

_________________
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

Changing the offset to +9 worked for me - thanks for the pointer.
Now all I need to do is find some time to move to r5.5

Cheers

Devsy

Hi there,

I'm a developer of Shepherd, the Aussie guide grabber. I just stumbled across this forum and saw a lot of people using Shepherd (and having problems with it), so thought I'd stick my head in.

I don't think any devs use Knoppmyth, so I'd like to hear about any distro-specific issues. Shepherd has maintained an uninterrupted supply of high-quality guide data for more than a year now on standard installs, and we'd like to make sure this is the case on Knoppmyth too.

We also have a friendly, helpful mailing list I encourage anyone here to join: http://www.interlink.com.au/mailman/listinfo/shepherd

Cheers,

Max.

Hi Max,

First of all, thanks for all the effort on shepherd, it's been my choice of EPG config for a while now, and i've not had that many problems at all.

The change in recommended way to "hook up" shepherd to mythfilldatabase caught me by surprise, only got it by chance (on the shepherd wessite) as i was surfing about a bit.

Something that i've had to look into recently is using a "re-nice" script to make sure all non-playback backend functions are not interfering with playback. I'd appreciate a list of the process names that shepherd calls to make sure i'm renicing all of them in my customised script at http://knoppmyth.net/phpBB2/viewtopic.php?t=19126&highlight=

Thanks again, i'm sure this thread will kick off again when DLS kicks in over here in Perth!

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

Great, glad to hear it.

That's funny, that was actually just addressed today. The default cron job to run Shepherd (the one created during installation, or by --configure-mythtv) will now "nice" the call to mythfilldatabase. This flows on to Shepherd and its components. So you shouldn't have to renice anything; just re-run --configure-mythtv. But let me know if this doesn't work.


Yeah, always fun, isn't it? There are about a thousand ways to get it wrong. Even after we ironed out the kinks in Shepherd, the datasources still muck it up.

Hi again,

So issuing the --configure-mythtv option like
./shepherd --configure-mythtv

will update the crontab? Do i have to update shepherd first somehow?

FYI, from what i can determine the latest version of KM (R5.5) has more recent tzdata debs, so has not seen the problems with DLS that the previous KM version (R5F27). Could be way off-base there, it wouldnt be the first time.

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

Right. Although somebody on the mailing list reported problems with this on Knoppmyth, so if it doesn't work, I'd like to see why not.


Generally no, since Shepherd is self-updating, but it wouldn't hurt to run an --update first, since I just added this code a few hours ago.

Cool, i'll give it a go tonight... although, its Friday, and that means dinner, a glass if wine, and falling asleep on the couch..

Thanks again for you and your fellow dev efforts

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

Hi Shepherd,

I try running the update and get an error as shown below



$sources in the conf file is a http link to shepherd:


After stopping the process and not having an idea about a package name, I let the update run through and it looked like all was well. Is there something I should be looking out for?

Thanks

This is a common error, related to a bad install.

You ran an old version of Shepherd (v1.2.40), and it tried to read a newer Shepherd config file ('sources' was introduced in v1.3.0). You most likely have multiple copies of Shepherd on your system, and didn't run the one you mean to.

From your output, you executed the command "shepherd --update" in your ~mythtv home dir. If Shepherd was installed properly on your system, that wouldn't do anything: wouldn't even find Shepherd. (You would instead invoke it like "tv_grab_au --update", using the system symlink /usr/bin/tv_grab_au, or "~/.shepherd/shepherd --update", calling it direct). You probably have a symlink called 'shepherd' lying around somewhere: see if you can track it down with "which shepherd" and delete both it and the old Shepherd it points to.

Many people wound up with multiple Shepherds because in early versions you were required to install it as the same user your MythTV runs it as: if you guessed this wrong, you got Shepherds all over the place. Nowadays, you can install Shepherd as whichever user you like.