From owner-freebsd-stable Sat Sep 14 2:17:23 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AE2C37B4B9 for ; Sat, 14 Sep 2002 02:15:59 -0700 (PDT) Received: from mail.dfwgroove.com (216-73-99-183.ocdc-01.net [216.73.99.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 153544415C for ; Sat, 14 Sep 2002 00:51:51 -0700 (PDT) (envelope-from jon.longoria@dfwgroove.com) Received: from aristotle [65.189.227.37] by mail.dfwgroove.com with ESMTP (SMTPD32-7.07) id AB431F6011A; Sat, 14 Sep 2002 00:54:43 -0700 Message-ID: <00a101c25bc3$ac8bf940$0c01a8c0@aristotle> From: "Jon Longoria" To: References: <20020914060706.ZPFI9549.out019.verizon.net@[127.0.0.1]> <007801c25bba$180a0630$0c01a8c0@aristotle> Subject: Re: ';;' instead of 'fi' Date: Sat, 14 Sep 2002 02:52:27 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Disposition-Notification-To: "Jon Longoria" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have found the solution to the error I received. I began playing around with the code, and realized, the string had not been terminated properly. ---------------------------------------------------------------- The original error encountered after mergemaster: ---------------------------------------------------------------- add net default: gateway x.x.x.x Additional routing options: TCP keepalive=YES. Routing Daemons:. Additional daemons: syslogd. /etc/rc: 427: Syntax error: ";;" unexpected (expecting "fi") Enter full pathname of shell or RETURN for /bin/sh: ---------------------------------------------------------------- The correct segment of code should look like this: ---------------------------------------------------------------- # Enable dumpdev so that savecore can see it. # /var/crash should be a directory or symbolic link # to the crash directory if core dumps are to be saved. if [ "${dumpdev}" != 'NO' ]; then case ${dumpdir} in '') dumpdir='/var/crash' ;; [Nn][Oo]) dumpdir='NO' ;; esac if [ "$[dumpdir]" != 'NO' ]; then echo -n 'Checking for core dump: ' /sbin/savecore ${savecore_flags} "${dumpdir}" fi fi if [ -n "${network_pass1_done}" ]; then network_pass2 fi ---------------------------------------------------------------- As compared to the original, which looked like: ---------------------------------------------------------------- # Enable dumpdev so that savecore can see it. # /var/crash should be a directory or symbolic link # to the crash directory if core dumps are to be saved. if [ "${dumpdev}" != 'NO' ]; then case ${dumpdir} in '') dumpdir='/var/crash' ;; [Nn][Oo]) dumpdir='NO' ;; esac if [ "$[dumpdir]" != 'NO' ]; then echo -n 'Checking for core dump: ' /sbin/savecore ${savecore_flags} "${dumpdir}" fi ;; esac if [ -n "${network_pass1_done}" ]; then network_pass2 fi I am unaware if anyone has duplicated this issue ever. But for arguments sake, I've posted my initial findings anyways. Thanks to those who gave my some personal insights and thoughts on the problem. Jon Longoria Senior Web Developer DFW Groove Productions ----- Original Message ----- From: "Jon Longoria" To: Cc: Sent: Saturday, September 14, 2002 1:43 AM Subject: Re: ';;' instead of 'fi' > Sure, it goes as follows: > > -------- > > add net default: gateway x.x.x.x > Additional routing options: TCP keepalive=YES. > Routing Daemons:. > Additional daemons: syslogd. > /etc/rc: 427: Syntax error: ";;" unexpected (expecting "fi") > Enter full pathname of shell or RETURN for /bin/sh: > > -------- > > Sorry but I am typing this between the machine and the client I am emailing > from. I was about to finally access /etc/rc and check line 427 and heres the > segment of code it was included in: > > # Enable dumpdev so that savecore can see it. > # /var/crash should be a directory or symbolic link > # to the crash directory if core dumps are to be saved. > if [ "${dumpdev}" != 'NO' ]; then > case ${dumpdir} in > '') > dumpdir='/var/crash' > ;; > [Nn][Oo]) > dumpdir='NO' > ;; > esac > if [ "$[dumpdir]" != 'NO' ]; then > echo -n 'Checking for core dump: ' > /sbin/savecore ${savecore_flags} "${dumpdir}" > fi > ;; <===( +++ NOTE: LINE 427 +++ ) > esac > if [ -n "${network_pass1_done}" ]; then > network_pass2 > fi > > Jon Longoria > Senior Web Developer > DFW Groove Productions > > > ----- Original Message ----- > From: > To: "Jon Longoria" > Cc: > Sent: Saturday, September 14, 2002 1:07 AM > Subject: Re: ';;' instead of 'fi' > > > > > > > > > Yea, i was trying to bring it up to check that line, but both vi and ee > > > won't show to console proper, so its a bit of a catch22 for me. > > > > > > > > Yup. I See. It might help if you post the three or four lines before the > error to give people an idea where in the process it was when it blew up. > > > > Gene > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message