True. The other plausible explanation is that the writer of this intended to search a file named "server.log" for a string/regexp he just forgot to write. This would mean the statement is equally incorrect, but so for a different reason.

Code:

grep '<missing regexp>' -A 999999 server.log

In any way, your solution is preferable to this, albeit in case the intended purpose was like i said it would have to be modified slightly:

Code:

sed -n '/<missing regexp>/,$ { /Option=\[Yes]/p; }' server.log | wc -l

I hope this helps.

bakunin