Date: Sat, 14 Sep 2002 02:52:27 -0500 From: "Jon Longoria" <jon.longoria@dfwgroove.com> To: <freebsd-stable@freebsd.org> Subject: Re: ';;' instead of 'fi' Message-ID: <00a101c25bc3$ac8bf940$0c01a8c0@aristotle> References: <20020914060706.ZPFI9549.out019.verizon.net@[127.0.0.1]> <007801c25bba$180a0630$0c01a8c0@aristotle>
next in thread | previous in thread | raw e-mail | index | archive | help
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" <jon.longoria@dfwgroove.com>
To: <glbj@verizon.net>
Cc: <freebsd-stable@freebsd.org>
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: <glbj@verizon.net>
> To: "Jon Longoria" <jon.longoria@dfwgroove.com>
> Cc: <freebsd-stable@freebsd.org>
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00a101c25bc3$ac8bf940$0c01a8c0>