On Thursday 24 March 2005 23:53, Hamish Moffatt wrote: > On Thu, Mar 24, 2005 at 03:27:01PM -0700, Blammo wrote: > > On Thu, 24 Mar 2005 15:23:07 -0700, Blammo <blammo.doh@xxxxxxxxx> wrote: > > > I'm planning on taking the data that femon puts out, and pulling it > > > into a graph or database. In order to do that, I needed a date/time > > > stamp. Here's my patch to femon.c to make this happen: > > > > Output looks like this when run: > > > > [root@backend1 szap]# ./femon > > using '/dev/dvb/adapter0/frontend0' > > FE: Nextwave nxt2002 VSB/QAM frontend (TERRESTRIAL) > > Mar 24 15:24:46 | status 1f | signal fd10 | snr e334 | ber 00000018 | > > unc 00000000 | FE_HAS_LOCK > > (Your mailer wrapped that.) > > :( Keep it to one 80-column line please. ie reject this patch. Agreed, since this is a feature that most people do not need, I would suggest that you replicate the internals of femon to suit your data capturing needs. On the other side of argument, the ber and unc fields is probably oversized, and could be reduced, but this is a binary incompatible change. So it's not really feasible in the real world :( I would guess that something like: time status signal snr ber unc status Mar 24 15:24:46 1f fd10 e334 00000018 00000000 FE_HAS_LOCK Mar 24 15:24:47 1f fd10 e334 00000018 00000000 FE_HAS_LOCK Would work.. Kenneth
