On 11/09/2014 03:19 PM, Philip Guenther wrote: > On Sun, Nov 9, 2014 at 2:33 PM, Jason Adams <[email protected]> wrote: >> On 11/09/2014 02:30 PM, h410g3n wrote: >>> I encountered the same problem. >>> >>> You must have just upgraded from 5.5 and forgot to run sysmerge, right? :D >>> >>> Jason Adams wrote: >>>> Everytime /etc/netstart runs I get a no closing quote message. >>>> >>>> Hate to obsess about trivialities but wondering If I've messed something >>>> up. >>>> All interfaces seem to work just fine. >> Did upgrade. >> Did NOT forget to run sysmerge. >> >> That's the google answer, but its not the REAL answer. > It's also the "crystal ball at the shop for repairs" answer when > there's no data in the report. > > Since you didn't show them, I'll take the next guess with "you have a > quoted string in an /etc/hostname.* file which contains whitespace". > > (If that's the case, I think the solution depends on which the string > is there for, but why guess when you can just show a (possibly > redacted) version?) > > > And if *that's* not the case, then how about you run /etc/netstart > with sh -x and debug it? > > > Philip Guenther Definitely no quoted anything with white space in any hostname.if. If fact even when they only have one parameter: dhcp, this happens.
And it happens very near the top of netstart ----------------------- # sh -x /etc/netstart + [ -n ] + . /etc/rc.d/rc.subr + FUNCS_ONLY=1 + [ -n 1 ] + return + _rc_parse_conf /etc/netstart: no closing quote ----------------------- It even happens when you give it a non-existent hostneme file: --------------------- # sh -x /etc/netstart aex0 + [ -n ] + . /etc/rc.d/rc.subr + FUNCS_ONLY=1 + [ -n 1 ] + return + _rc_parse_conf /etc/netstart: no closing quote + [ 1 -gt 0 ] + [ 1 -gt 0 ] + ifstart aex0 netstart: /etc/hostname.aex0: No such file or directory + shift + [ 0 -gt 0 ] + return # --------------------------- -- Those who do not understand Unix are condemned to reinvent it, poorly.
