Question: is the error string ALWAYS specifically begin with, 'INVALID ORDER ...', or are there other error messages, too? If other kinds of errors may appear (with or without a leading /path/and/filename), then I would recommend grep's solution -- remove the offending path, leaving the rest.

Of course, if the ONLY error message you will get ALWAYS starts with 'INVALID ORDER ', then the solution can be made even less prone to mismatches (just take 'INVALID ERROR ' and anything that follows it):

<CODE> s/(INVALID ORDER .*)$/$1/;

dmm

If you GIVE a man a fish you feed him for a day
But, TEACH him to fish and you feed him for a lifetime

In reply to Re: A poor bloke and his regex... by dmmiller2k
in thread A poor bloke and his regex... by vek

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.