Shell Programming and Scripting

Can you post output of:

Code:

cat -eT switch1.txt

It never takes long before there's something I can't do on OS X that could normally be done on a true *nix box. I couldn't do the -T switch but I could do a lower-case -t switch. For whatever it's worth, here's the output from that:

$ cat -eT switch1.txt | awk '/ntp/'
cat: illegal option -- T
usage: cat [-benstuv] [file ...]

$cat -et switch1.txt | awk '/ntp/'
ntp server 10.10.250.2^M$
ntp server 10.10.250.1 prefer^M$

Tell you anything valuable?

Does your Mac have dos2unix utility?

No, but what do you think about the final two posts in this thread:

Convert end-of-line characters (revisited) - Mac OS X Hints

It appears there're many ways to go about this, so if you could be so kind as to point out what I'm to replace (and what with), I'm sure I can get it done. Heck, maybe I can get it done during the creation of these .txt files (I'm generating them via a TCL script that calls Expect and does a bunch of interactive stuff to give me not only the configs, but a bunch of 'show processor cpu history' and so forth). Evidently that process is fouling up the EOL or something?

Try this:

Code:

perl -nle 's/\x0d$//;printf "$ARGV," if $.==1;printf "$_," if /ntp server/;if (eof){$.=0;printf "\n"}' * > out.csv

Yes, the above does work quite nicely! It gives me an output file in about one second, which isn't bad considering I have roughly 200 .txt files (some of which are quite large) in the directory.

However, I'm even less Perl aware than I am grep/awk aware, so I really have no idea what the above does or how. I have many, many applications for such as script, so I'm hopeful to walk away from all of this with a template that can be adapted/evolved. Not knowing much about Perl at all, I fear I would have to seek help getting anything new out of the above. Can you please help me to understand it, at least on a high level? I won't be the least bit offended if you say "no" - you've already given of your time.

agama,

I suppose this whole EOL thing made perfect sense to you all along. Is there now a tweak to your code that would work? I'm not sure what I have to do in order to get xargs going but I'll shortly find out...

---------- Post updated at 01:04 PM ---------- Previous update was at 01:03 PM ----------

Oh, and can I limit the above to just files in the directory with .txt extensions?

You don't need to use a stand alone utility to trash the carriage-return characters when using an awk to parse your data. Just add an extra gsub() and that should work:

Code:

awk '
    BEGIN { n = 0; k = 1; }

    FILENAME != last {
        fn = FILENAME;
        gsub( ".txt", "", fn );
        printf( "%s%s%s", k ? "" : ",", n ? "\n" : "",  fn );
        last = FILENAME;
        n = 1;     # signal need for newline before fn (prevent lead newline)
        k = 0;     # when set, signals comma
    }

    /ntp server/ || /ntp peer/ {
        gsub( "\r", "", $0 );           # ditch the charriage return
        printf( ",%s", $0 );
        k = 1;
    }

    END {
        printf( "%s\n", k ? "" : "," );
    } '  *.txt