Hi tcf03

if your config file is always that simple, you could use a regex to parse it, like 

#!/usr/bin/perl -l

use strict;
use warnings FATAL => "all";

my $stuff;

{
$/= undef;

 $stuff = <DATA>;
}
while ($stuff =~ /<server>\n(.*?)<\/server>/msg){


        print join ",", split "\n", $1 ;
}


__DATA__
<server>
printserver1
default
cups
cups
</server>
<server>
printserver2
no
aix
rsh
</server>

__END__

this returns

printserver1,default,cups,cups
printserver2,no,aix,rsh

[download]

If it can get much more complicated than this, you may have to consider alternatives

I hope this helps

thinker

In reply to Re: Parsing a config file by thinker
in thread Parsing a config file by tcf03

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.