lofty69 at gmail
Apr 24, 2012, 1:10 PM
Post #10 of 12
On 24 April 2012 21:05, Gavin Hurlbut <gjhurlbu [at] gmail> wrote:
> On Tue, Apr 24, 2012 at 12:51 PM, Roy Lofthouse <lofty69 [at] gmail> wrote:
>> warning is fine for me and it's easily changed if need be.. however it
>> looks like the mythshutdown check may be hardcoded somewhere as I
>> searched my db and can only find one ref to mythshutdown
>> (preSDWUCheckCommand), but this was calling --check where the one
>> doing all the logging is called with -status (would be nice if this
>> took it's settings from mythbackend or you could pass your own on).
> This is coming from mythwelcome calling it, I believe. As far as I
> know, one of the other devs is looking at combining all that
> functionality so we don't need mythwelcome and mythshutdown at all
> anymore. I'm not sure where that lays in the plans though.
>> It's just annoying seeing all entries filling up every 30 seconds.
> Then stop looking at them :) Seriously though, I don't use
> mythshutdown at all, and I don't expect you will see much action in
> making it "better" before it's removed.
> Alternatively, you can hunt down where in mythwelcome is spawning it,
> and remove the logging propagation from the arguments, and it should
> happily not log at all (you will have to say --nodblog though).
> mythtv-users mailing list
> mythtv-users [at] mythtv
just added a new mythshutdown bash script that calls mythshutdown (now
mythshutdownbin) with -c none :) Will do for now.
Thanks for your time Gavin. Much appreciated.
mythtv-users mailing list
mythtv-users [at] mythtv