Hi
On Tue, Feb 26, 2008 at 3:48 PM, Ben Caldwell <[EMAIL PROTECTED]> wrote:
> The log file is probably not able to be accessed by mythbackend because it
> is running as a user and the log file is owned by root.
> The thread with the subject "[ATrpms-users] Mythbackend will not start after
> upgrad
The log file is probably not able to be accessed by mythbackend because it
is running as a user and the log file is owned by root.
The thread with the subject "[ATrpms-users] Mythbackend will not start after
upgrade to Mythtv ver 174" contains some fixes for this if you are
interested.
Regards,
B
Hi
On Tue, Feb 26, 2008 at 8:45 AM, Jean-Yves Avenard <[EMAIL PROTECTED]> wrote:
>
> 176 is a disaster.
> It crashed so often.
> mythfrontend generates so much errors / warning when watching a TV
> channels that it managed to fill 6GB of logs in a few hours...
Happy to report that 177 works m
On Mon, Feb 25, 2008 at 9:57 PM, Ben Caldwell <[EMAIL PROTECTED]>
wrote:
> Just remembered another fix I had to make, because mythbackend is now
> running as user rather than root, you may need to change the permissions of
> the /var/logs/mythtv/mythbackend.log file so that the mythtv user can wri
On Mon, Feb 25, 2008 at 7:53 PM, Ben Caldwell <[EMAIL PROTECTED]>
wrote:
> I just fixed this myself last night, the problem here seems to be that an
> export command must not have the $ before the variable (this is from my own
> experiences with Fedora 8, not sure if this is distro specific).
>
>
Just remembered another fix I had to make, because mythbackend is now
running as user rather than root, you may need to change the permissions of
the /var/logs/mythtv/mythbackend.log file so that the mythtv user can write
to it!
Regards,
Ben Caldwell
On Tue, Feb 26, 2008 at 9:53 AM, Ben Caldwell
I just fixed this myself last night, the problem here seems to be that an
export command must not have the $ before the variable (this is from my own
experiences with Fedora 8, not sure if this is distro specific).
The fix: in /etc/init.d/mythbackend find the part that says "export $HOME"
and cha
Hi
On Tue, Feb 26, 2008 at 5:31 AM, John Pilkington <[EMAIL PROTECTED]> wrote:
> I just did a 'smart' upgrade from 175 to 177. No obvious problem in
> starting Mythtv and my problem with the radio stations has gone away.
>
176 is a disaster.
It crashed so often.
mythfrontend generates so much
I just did a 'smart' upgrade from 175 to 177. No obvious problem in
starting Mythtv and my problem with the radio stations has gone away.
There was a host of other upgrades too - total download was 70MB - and
they may have helped, but a big thankyou to Axel and the devs for all this.
John P
Jeffrey J. Kosowsky schreef op 25-2-2008 15:42:
> I upgraded to 172 late last week and noticed this morning that 174 is
> available (I assume that somehow I missed a short-lived 173 upgrade).
>
> Given the reported 174 problems, should I just hold off on upgrading
> until a new version is releas
Paulo Cavalcanti wrote at about 09:45:41 -0300 on Monday, February 25, 2008:
> On Mon, Feb 25, 2008 at 9:34 AM, O&M Ugarcina <[EMAIL PROTECTED]> wrote:
>
> > Hello Axel,
> >
> > I just took the latest myth update ver 174 on my FC 8 box . After
> > completing the update with yum I restarted t
O&M Ugarcina schreef op 25-2-2008 14:15:
> Anthony Messina wrote:
>> On Monday 25 February 2008 06:50:10 am Anthony Messina wrote:
>>
>>> you don't need to. just comment out the following line
>>> in /etc/init.d/mythbackend:
>>> daemon --user mythtv $binary $OPTIONS
>>>
>>
>> the above wor
Anthony Messina wrote:
On Monday 25 February 2008 06:50:10 am Anthony Messina wrote:
you don't need to. just comment out the following line
in /etc/init.d/mythbackend:
daemon --user mythtv $binary $OPTIONS
the above works, but skip this part:
and add a $ befo
Anthony Messina wrote:
On Monday 25 February 2008 06:45:41 am Paulo Cavalcanti wrote:
On Mon, Feb 25, 2008 at 9:34 AM, O&M Ugarcina <[EMAIL PROTECTED]> wrote:
Hello Axel,
I just took the latest myth update ver 174 on my FC 8 box . After
completing the update with
On Monday 25 February 2008 06:50:10 am Anthony Messina wrote:
> you don't need to. just comment out the following line
> in /etc/init.d/mythbackend:
> daemon --user mythtv $binary $OPTIONS
the above works, but skip this part:
> and add a $ before HOME in the "export HOME" just a few lines above
On Monday 25 February 2008 06:45:41 am Paulo Cavalcanti wrote:
> On Mon, Feb 25, 2008 at 9:34 AM, O&M Ugarcina <[EMAIL PROTECTED]> wrote:
> > Hello Axel,
> >
> > I just took the latest myth update ver 174 on my FC 8 box . After
> > completing the update with yum I restarted the machine . The machin
On Mon, Feb 25, 2008 at 9:34 AM, O&M Ugarcina <[EMAIL PROTECTED]> wrote:
> Hello Axel,
>
> I just took the latest myth update ver 174 on my FC 8 box . After
> completing the update with yum I restarted the machine . The machine
> seemed to come back ok until I tried to use it . I noticed that
> My
Hello Axel,
I just took the latest myth update ver 174 on my FC 8 box . After
completing the update with yum I restarted the machine . The machine
seemed to come back ok until I tried to use it . I noticed that
Mythbackend was down and when trying to restart it I got the following :
[EMAIL PRO
Nick Morrott schreef op 24-2-2008 23:41:
> On 24/02/2008, Axel Thimm <[EMAIL PROTECTED]> wrote:
>> On Sat, Feb 23, 2008 at 09:56:05PM +0100, Jos Hoekstra wrote:
>> > Err sorry, was talking about xmltv. The new one doesn't contain the
>> > grabber for NL anymore and would still like to use till th
19 matches
Mail list logo
