Sunday, May 6, 2012

How to flush dns on ubuntu 12.10


Update the below search and info did not help me flush the dns. I had to reboot my router and that helped flush the dns on chrome. The setting on chromium did not work .

google is still shitty and shows an old 2008 document. the commands on that doc DO NOT WORK
http://www.ubuntugeek.com/howto-clearflush-dns-cache-in-ubuntu.html


The best help on that link was the comments
In any case, nscd is NOT installed by default in Ubuntu. It makes absolutely no sense to install it, only to be able to reset it. If it is not installed, then DNS is not cached directly by libc. Firefox, for example, maintains its own DNS cache, and the only way to clear it is to restart the browser. The OS does not cache DNS unless you install nscd manually, as this article advocates. It’s just common sense here, people


The dns-clean service runs at every boot, so a simple reboot of Ubuntu cleans out your DNS anyway.


open the terminal and type
sudo /etc/init.d/networking restart

google search flush dns chromium

the first link google shows is the confusing
http://superuser.com/questions/203674/how-to-clear-flush-the-dns-cache-in-google-chrome

so i search through that and try out
DNS Flusher for Chrome
https://chrome.google.com/webstore/detail/fegcjmebpcoihkfdjilmnemfkgjbneol

DNS Flusher for Chrome

Option:

Auto reload:Reload current page after refreshing DNS cache.

Attention:

Command-line flag "--enable-benchmarking" must be used to start chrome.

Windows:

your_chrome_path/chrome.exe --enable-benchmarking

Linux:

google-chrome --enable-benchmarking

where the F** do i add this command
in the terminal when you type  google-chrome --enable-benchmarking
error !  google-chrome: command not found
Mac:

open /applications/google\ chrome.app --args --enable-benchmarking


so i google this shitty plugin

Command-line flag "--enable-benchmarking" must be used to start chrome.

Warning:  Looks like you forgot to run chrome with  --enable-benchmarking set.

Instructions



Option 1:  Use the benchmark from the chromium source code
The benchmark is part of the chromium source code.  You'll find it here:  
\src\chrome\common\extensions\docs\examples\extensions\benchmark
    



To run Chrome with the benchmark, use the following command line:
    chrome.exe --enable-benchmarking --load-extension=\src\chrome\common\extensions\docs\examples\extensions\benchmark

Option 2: Install from Chrome Extension GalleryInstall the extension from Chrome Extension Gallery following this link.

Then you'll need to restart the browser to use it.
When you run chrome, use:
    chrome.exe --enable-benchmarking

I still cannot figureout how to run google chrome command line flags

http://www.chromium.org/developers/how-tos/run-chromium-with-flags
http://peter.sh/experiments/chromium-command-line-switches/


To use a command line switch:

On Windows:

  1. Right click on your "Chrome" icon.
  2. Choose properties
  3. At the end of your target line, place these parameters:
    • --remote-debugging-port=9222
  4. It should look like: chrome.exe --remote-debugging-port=9222
On OS X:
/Applications/Chromium.app/Contents/MacOS/Chromium --remote-debugging-port=9222

# for Google Chrome you'll need to escape spaces like so:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222

On Linux:
chromium-browser --remote-debugging-port=9222



so this finally works

chromium-browser --remote-debugging-port=9222


~$ chromium-browser --remote-debugging-port=9222

Created new window in existing browser session.


chromium-browser --enable-benchmarking
chromium-browser --enable-benchmarking

Created new window in existing browser session.





Current switches may be found at http://peter.sh/examples/?/chromium-switches.html
It is important to note that using these switches is not supported or recommended. They should only be used for temporary cases and may break in the future.


To use a command line switch:


On Windows:
Right click on your "Chrome" icon.
Choose properties
At the end of your target line, place these parameters:
--remote-debugging-port=9222
It should look like: chrome.exe --remote-debugging-port=9222
On OS X:
/Applications/Chromium.app/Contents/MacOS/Chromium --remote-debugging-port=9222


# for Google Chrome you'll need to escape spaces like so: 
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222


On Linux:
chromium-browser --remote-debugging-port=9222





No comments:

Post a Comment