>Do you have another flavor of awk available to try? I still doubt that >it's gawk's fault, but we need to eliminate possibilities.
I ran with nawk (/usr/bin/nawk) & the parse error went away. Is their any way I can check if the awk output is valid (is their anything I can check for or compare with) ? Thanks for your help, Ralph Lecessi > ---------- > From: Tom Lane[SMTP:[EMAIL PROTECTED]] > Sent: Tuesday, May 21, 2002 11:17 AM > To: Lecessi, Ralph > Cc: [EMAIL PROTECTED] > Subject: Re: [BUGS] Bug #669: gawk: cmd. line:2: (END OF FILE) > > "Lecessi, Ralph" <[EMAIL PROTECTED]> writes: > > Sun OS 5.6 > > /bin/sh is a Bourne shell. > > Hmph. Nothing particularly unusual-seeming about that. > > Do you have another flavor of awk available to try? I still doubt that > it's gawk's fault, but we need to eliminate possibilities. > > Another thing to check is whether you might have a corrupted copy of > genbki.sh. In 7.2.1 I get these numbers from "wc genbki.sh": > 424 1609 10863 > If yours match then it's probably okay. > > regards, tom lane > ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html