[mythtv-users] What Tuner Did a Recording Come From?
watkinshome at gmail.com
Wed Sep 14 10:25:33 UTC 2011
On 13 September 2011 17:49, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> On 09/13/2011 09:15 AM, David Watkins wrote:
>>> FWIW, I don't see any possible way that this message won't be written on
>>> any system--other than by disabling general messages.
>> I also don't see any "Started recording" messages in my backend log.
>> I'm running v0.25pre-3072-g50606cd without any -v arguments set,
>> although I do have --nodblog (can't remember why I did that!).
> The message is also written out in master at general. The format is
> slightly different, though, so I'll likely have to fix the regex when
> 0.25 is released and I upgrade to it. (Unless someone else beats me to
> it--but please make sure you don't break the regex for 0.24 and previous
> Still, I can't see any reason why it wouldn't be output. I'd need some
> default-verbosity logs to even start guessing.
I'm not really concerned about it but if you're interested here's a
snippet of my backend log at the start of a recording:
19:00.199263 I [1741/1839] TVRecEvent tv_rec.cpp:992
(HandleStateChange) - TVRec(1): Changing from None to RecordingOnly
19:00.202624 I [1741/1839] TVRecEvent tv_rec.cpp:3434
(TuningCheckForHWChange) - TVRec(1): HW Tuner: 1->1
19:00.407682 I [1741/3680] DVBRead mythdbcon.cpp:479 (CloseDatabases)
- Closing DB connection named 'DBManager261'
19:00.984423 N [1741/1848] Scheduler autoexpire.cpp:263 (CalcParams) -
AutoExpire: CalcParams(): Max required Free Space: 3.0 GB w/freq: 14
19:00.984514 I [1741/1848] Scheduler scheduler.cpp:2466
(HandleRecordingStatusChange) - Tuning recording: Tootsie: channel
1002 on cardid 1, sourceid 1
19:02.169288 I [1741/1741] CoreContext scheduler.cpp:611
(UpdateRecStatus) - Updating status for Tootsie on cardid 1 (Tuning =>
19:02.317913 I [1741/1839] TVRecEvent tv_rec.cpp:3948
(TuningNewRecorder) - TVRec(1): rec->GetPathname():
19:02.438414 I [1741/3692] DVBRead mythdbcon.cpp:75 (MSqlDatabase) -
Database connection created: DBManager262
19:02.438511 I [1741/3692] DVBRead mythdbcon.cpp:298 (popConnection) -
New DB connection, total: 15
19:02.440236 I [1741/3692] DVBRead mythdbcon.cpp:179 (OpenDatabase) -
Connected to database 'mythconverg' at host: localhost
I believe mythbackend is running with default verbosity.
# ps -ef | grep mythbackend
root 1712 1 5 10:19 ? 00:03:26
/usr/local/bin/mythbackend --daemon --nodblog --logfile
/var/log/mythtv/mythbackend.log --pidfile /var/run/mythbackend.pid
I put the --nodblog option it to try and remove the mythdbcon.cpp
messages. I'm guessing that these are diagnostic messages temporarily
added to trunk?
More information about the mythtv-users