Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Error on one line' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Error on one line
Authored by: SCID on Dec 20, '01 11:09:02PM
on this line
tail -n10 rndc.conf | head -n9 | sed -e s/# //g >> named.conf
I get the following error
sed: 1: "s/#": unterminated substitute pattern
any ideas sam d

[ Reply to This | # ]
Error on one line
Authored by: dlandrith on Dec 20, '01 11:36:08PM
There should be a backslach immediately following the poundsign. This will escape the space that follows. Escaping the space causes the space to be part of the pattern rather than a string terminator. The backslash was in the original, but for some reason it fails to show up on the page (it also wouldn't show up on the preview of this comment). At any rate, I've inserted the HTML entity for the backslash in the following command (this does show up in the preview):

tail -n10 rndc.conf | head -n9 | sed -e s/#\ //g >> named.conf

If it still doesn't show up above, just insert the backslash immediately after the pound sign.

The purpose of sed portion of the above command is to remove the comments from the part that we are adding to the end of named.conf. Thus, another workaround is leave out the sed portion as follows:

tail -n10 rndc.conf | head -n9 >> named.conf

And then remove the comment marks (the pound sign and space at the start of each of the last 9 lines of the named.conf file using your favorite console editor.

I hope this helps.



[ Reply to This | # ]

Error on one line
Authored by: SCID on Dec 21, '01 12:19:03AM

Worked great thanks. Definately speeds up my broadband (sprint fixed wireless) addresses some of the latency issues that seem to be in this method of connection. After the first hit things are much snappier



[ Reply to This | # ]
Fixed in main story...
Authored by: robg on Dec 21, '01 09:23:06AM

Thanks for the find; I've now added the backslash to the main article. Geeklog (the site engine) loves to eat backslashes (and less-than and greater-than signs as well).

The only way to post them is to use HTML entities, but even then, they get converted to the real character in the preview, so after one preview, you have to re-do the entities.

I'm hoping this gets fixed in the new Geeklog, due out shortly.

-rob.



[ Reply to This | # ]