SUZANA BT ZAHRI <suzana(_at_)kym(_dot_)edu(_dot_)my> writes:
...
Testing for memmove, strchr, strpbrk, strcspn, strtol, strstr,
rename, setrgid, setegid, pow, opendir, mkdir & waitpid
Determining the maximum number of 16 byte arguments execv() takes
Benchmarking your system's strstr() implementation
Waiting for the kernel-locking tests to finish...
Every two digits a file is locked. First digit: which file, second digit:
which program, XX indicates a lock conflict or failure...
looks to me like something not right is amiss..anyway i let it run, then
Those messages are generated by procmail's autoconf script which is just
checking to see whether your system is missing something that procmail
will have to emulate and which kernel-locking methods are functional.
when i checked the procmail binary, i saw this at the end of the file:
"procmail" [Incomplete last line] 449 lines, 82088 characters (23337 null)
Um, yes. procmail is a binary, not a text file. You don't open
binaries in vi, but rather run them. If you try it, you'll find that
practically every binary on the system has an 'incomplete last line'.
All that means is the last character in the file is not a newline.
The real question is: what's the output of
path/to/procmail -v
Philip Guenther
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail