[Xastir] DBFAWK - Doin' it wrong?

[km5vy Tom Russo]

On Tue, Mar 24, 2020 at 10:45:29AM -0600, we recorded a bogon-computron collision of the <russo at bogodyn.org> flavor, containing:
> On Tue, Mar 24, 2020 at 09:41:49AM -0700, we recorded a bogon-computron collision of the <curt.we7u at gmail.com> flavor, containing:
> > Yea, try it... I didn't see any filenames listed in the output.
> 
> I didn't say there would be.  But there will be a dbf signature shown, and 
> you use grep to find all the files in the config directory that have that
> signature.  For example:
> 
> 8 Columns,  3334 Records in file
> sig: STATE:CWA:COUNTYNAME:FIPS:TIME_ZONE:FE_AREA:LON:LAT
> DBF Signatures match!
> 
> 
> One then does:
> 
> grep -l 'dbfinfo="STATE:CWA:COUNTYNAME:FIPS:TIME_ZONE:FE_AREA:LON:LAT"' /usr/local/share/xastir/config/*
> 
> to get the list of file names that contain that signature.

Modifying testdbfawk.c to emit the file name sounds like a great idea until
you dig into how dbfawk works.

It does just what Xastir does:  starts up and calls "dbfawk_load_sigs" to read
in all the dbfawk files in the specified directory.  dbfawk_load_sigs reads
the file and creates a dbfawk_sig_info structure, then adds it to a linked 
list.

At this point, the name of the file from which the dbfawk info was obtained
is forgotten.  All future scanning of signatures is done by searching the linked
list.

To do as you suggest would require hacking the dbfawk_sig_info to retain
filename info and to change how dbfawk_load_sigs works.

Which seems a lot more work than running testdbfawk and using standard linux
tools to find all matching files.  The only reason for doing this is to find
all the files other than the one you WANT to use that may be used instead.
And it can be done now with no hacking.

> > On Tue, Mar 24, 2020 at 9:34 AM km5vy Tom Russo <russo at bogodyn.org> wrote:
> > >
> > > On Tue, Mar 24, 2020 at 09:32:02AM -0700, we recorded a bogon-computron collision of the <curt.we7u at gmail.com> flavor, containing:
> > > > On Tue, Mar 24, 2020 at 9:13 AM Curt Mills <curt.we7u at gmail.com> wrote:
> > > > >
> > > > > One could also turn on debug level 16. Might be of use in this case.
> > > >
> > > > Could also mess around with testdbfawk, although now that I think
> > > > about it we should think about modifying testdbfawk.c to print out the
> > > > name of the dbfawk file that matched the dbf file. Could be quite
> > > > useful in this case.
> > > >
> > > >   cd /usr/local/share/xastir; testdbfawk -D config -d
> > > > Counties/mz02ap19.dbf 2>&1 | head -10
> > >
> > > One could.  Or one could just run the command above and use "grep" to find
> > > all the files that have the same dbfinfo line.
> > >
> > > --
> > > Tom Russo    KM5VY
> > > Tijeras, NM
> > >
> > >  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]
> > >
> > 
> > 
> > -- 
> > Curt, WE7U        http://xastir.org        http://www.sarguydigital.com
> 
> -- 
> Tom Russo    KM5VY
> Tijeras, NM  
> 
>  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

-- 
Tom Russo    KM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]