Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!timbuk!cs.umn.edu!quest!ssb
From: ssb@quest.UUCP (Scott S. Bertilson)
Newsgroups: news.software.b
Subject: C news newgroup - awk failure
Message-ID: <10885@quest.UUCP>
Date: 30 Oct 90 19:45:36 GMT
Reply-To: ssb@quest.UUCP (Scott S. Bertilson)
Organization: Quest Research Inc., Burnsville, MN
Lines: 19


  I've had problems lately with "gnu.g++.bug" being inserted into my
active file every time a bogus "newgroup" comes across the net.
I had about 4 copies earlier today (in addition to the real one).
  It seems that "awk" and "nawk" aren't able to match the pattern:
	"^gnu\.g++\.bug "
against the newsgroup name.  I've found that it works if I change the
pattern to:
	"^gnu\.g\++\.bug "
or
	"^gnu\.g.+\.bug "
  I've tried this on SCO ODT, Altos UNIX SVR3.1, and a 3B1
running SVR1 (3.51).  I've changed my copy of "newgroup" to use
"sed" instead.  Here's my test line:
	echo 'gnu.g++.bug 00001 00001 y' | awk '/^gnu\.g++\.bug / {print}'
-- 

Scott S. Bertilson   ...ssb@quest.UUCP
			scott@poincare.geom.umn.edu