It all depends on the time period you have for analysis of those logs, and how time critical it all is.
C, if properly written and optimised will beat Perl, due to lower overheads.
However, if you're doing Regexp matches on those logs (and why else would you program them??), then I think the whole thing becomes moot.
As far as I'm aware, the C lib for pattern matching is only as fast as the Perl one. The advantages gained by using C become almost insignificant.
Looking at the spec of this, I'd go for Perl. It's likely to have fewer gotchas than an equivalent C program for a marginal extra system overhead.
And if, once you've proved the system, they want more and faster, then, Perl has just made an excellent prototyping language.

Just my tuppence worth. :)

Malk

*I lost my .sig. Do you have a spare?*

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.