[Wylug-discuss] Logging AT

[Stephen Franks]

At the risk of slipping off-topic, your DVBT problem sounds horribly familiar.

I had pretty much identical problems when I built my Freeview-basd MythTV recorder (around 2008). I found *lots* of discussions about it at the time, it was a common issue. As I recall it relates to USB errors when tuning, and I never saw a definitive fix, although there were lots of suggestions. For all suggested fixes, someone always claimed it didn't work for them (and nothing worked for me). Failing any proper fix, I cheated: I replaced my DVBT tuners with non-USB hardware. Not so easy now, I don't think anyone sells tuners that are not USB (internal cards still use USB, it just never appears on a connector).

I should note that at the time I knew next to nothing about Linux. I've come a way since then, but still a long way to go. :)

If you happen to find the cause I would be *very* interested! I've held off ever upgrading purely because of this problem.

If you'd like any references to the discussions I've seen let me know and I'll see if I've kept any links. A quick Google now finds http://ubuntuforums.org/showthread.php?t=1687846.

Regards,

Stephen

-----Original Message-----
From: wylug-discuss-bounces at wylug.org.uk on behalf of Paul Brook
Sent: Tue 17/04/2012 12:44
To: Mike Martin
Cc: wylug-discuss at wylug.org.uk
Subject: Re: [Wylug-discuss] Logging AT
 
> On 16 April 2012 18:25, Paul Brook <paul at codesourcery.com> wrote:
> >> Anyone got any ideas on how to get at to log the output of commands it
> >> runs? (using -m only logs some of it)
> > 
> > What exactly is it missing?  A quick test shows it working as expected
> > here, recording both stdout and stderr.
> > 
> > Paul
> 
> Some context, its a dvb recording app using a subset of
> Linux::DVB::DVBT module (perl)
> 
> and perhaps once in 25 for video and more often for audio only it
> doesnt tune properly, so far not been able to replicate it manually,
> so need to try to get info from at
> 
> The program runs for a period of time ie: runs for n seconds after
> launch, so the only output is at the end, not when at launches the
> program.

In all my tests at -m has done exactly what you want.

So I'll ask the question again: How does the at -m output differ from what 
you're expecting?

Paul

_______________________________________________
Wylug-discuss mailing list
Wylug-discuss at wylug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/wylug-discuss