[dsc] question about dnssec_qtypes in plot.pm

[Duane Wessels]

On Wed, 3 Nov 2010, Marco Davids (SIDN) wrote:

> On 11/03/10 17:21, Marco Davids (SIDN) wrote:
>
>>  dnssec_qtype => {
>>     dataset     => 'dnssec_qtype',
>>
>> Does this sound familiar?
>>
>> I checked an older version of DSC that I have running at home, and
>> DNSSEC qtype-data does end up there in two places: qtype.dat and
>> dnssec_qtype.dat.
>
> Mmmm, maybe not - I misinterpreted the .dat file I suppose. Probably
> wishful thinking... In any case the described change is not applied
> there, and things still work fine. Makes me wonder even more why we had
> to modify 'plot.pm' on the newer system to make it work there.

Hi Marco,

Looks like there is a bug and your first message was correct.  In
fact the "dataset" line should be removed from the dnssec_qtype
block because the data should be found in dnssec_qtype.dat (it has
the same name as the plot).

If you don't have a dnssec_qtype.dat file, then it sounds like
something is out-of-date in the extractor code.  The file
perllib/DSC/extractor/config.pm should look like this:

%DATASETS = (

   qtype => {
     ndim        => 1,
     type1       => 'Qtype',
     outputs     => {
       qtype => {
         keys    => [ qw(1 2 5 6 12 15 28 33 38 255 else) ],
         data_munger => \&main::munge_elsify,
         data_reader => \&DSC::extractor::read_data,
         data_merger => \&main::merge_trace,
         data_writer => \&DSC::extractor::write_data,
       },
       dnssec_qtype => {
         keys    => [ qw(24 25 30 43 46 47 50 48) ],
         data_munger => \&main::munge_elsify,
         data_reader => \&DSC::extractor::read_data,
         data_merger => \&main::merge_trace,
         data_writer => \&DSC::extractor::write_data,
       },
     },
   },


(yours may be missing "50" in the keys list because I just added it)

The above tells the extractor code to write a dnssec_qtype.dat
file containing the keys (query types) given in that list.

Duane W.