[mythtv-users] Upgrade 0.24->0.25 goes poorly.

[Michel Meyers]

On 13/05/2012 19:15, Bill Meek wrote:
> On 05/13/2012 11:57 AM, Ross Boylan wrote:
>> On Sun, 2012-05-13 at 11:13 -0500, Bill Meek wrote:
>>> On 05/12/2012 09:22 PM, Ross Boylan wrote:
>>> ...
>>>> /var/log/mythtv/mythbackend.log has not been touched since the upgrade,
>>>> and I don't see much in any logs.
> ...
>>> Check your /etc/init.d/mythtv-backend file. It will tell you where your
>>> logs are going. It won't be the file you looked at above. Expect:
>>>    --syslog sonething or --logpath somethingElse.
>> It is the file I looked at.  Here are the key parts of the init.d file
>>
>> DAEMON=/usr/bin/mythbackend
>> ARGS="--daemon --logpath /var/log/mythtv/mythbackend.log --pidfile
>> $RUNDIR/$NAME.pid"
>> start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \
>>                    --chuid $USER --nicelevel $NICE --exec $DAEMON --
>> $ARGS
> 
> --logpath must point to a directory, not a file. I understand from your
> original
> post that --help didn't help, so:
> http://www.mythtv.org/wiki/Logging#File_Logging.
> In other words:  --logpath /var/log/mythtv.

This seems to be a bug in the package as I had the same problem on my
box (The log path is hardcoded in the /etc/init.d/mythtv-backend script
and not updated when going from 0.24 to 0.25).

- Michel