|
|
Error on one line
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.
Error on one line
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
Fixed in main story...
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). |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.06 seconds |
|