* Dallman Ross <dman(_at_)nomotek(_dot_)com> [2005-01-08 12:30]:
I doubt it is procmail screwing things up. "segmentation" is a
suspicious word around operating systems. It usually has to do with
the phrase, "segmentation fault." (Do you have a second file called
"fault"?) Some program is barfing.
This turns out to be a defect in the most recent version of sed. Once
I got the log files seperated, I could see where the problem was.
Here are some tests that reveal the sed bug:
-- TEST RESULTS begin --
$ /bin/sed --version
GNU sed version 4.1.2
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE,
to the extent permitted by law.
$ echo some | /bin/sed -e 's/SOME/somephrase/I'
somephrase
$ echo som | /bin/sed -e 's/SOME/somephrase/I'
Segmentation fault
$ echo som | /bin/sed -e 's/SOME/somephrase/'
som
$ /bin/sed_405 --version
GNU sed version 4.0.5
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE,
to the extent permitted by law.
$ echo som | /bin/sed_405 -e 's/SOME/somephrase/I'
som
-- TEST RESULTS end --
So sed version 4.1.2 pukes on all case-insensitive replace operations
such that no match is found. Sed version 4.0.5 handles this
correctly.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail