Showing that lookupd -flushcache has done its job

Discussion in 'Apple' started by mark, Aug 19, 2007.

  1. mark

    mark Guest

    I have a small, but annoyingly growing, list of websites that I can't
    access - the connection just times out - on this machine running OS

    The standard response from various places on the web is to clear by
    cache using lookupd -flushcache (or variants of it including sudo) -
    but that's not worked. Is there any way to actually view the size of
    the cache to make sure it has cleared.

    If that's not it, where can the problem actually lie, and where is it
    most likely to be? My router? My ISP?

    mark, Aug 19, 2007
    1. Advertisements

  2. mark

    mark Guest

    Of the three that I currently can't get onto, two of them time out on
    a traceroute when they get to the hosts ( and I've just checked a third site that I've not been
    able to connect to in the last few days and the traceroute connects
    fine to that, so that may be a different issue.

    mark, Aug 19, 2007
    1. Advertisements

  3. mark

    hashmac Guest

    i tried sending a message did it post?

    I tried posting a reply -- it's not showing up -- WTF google?

    here is what I replied to you:

    there are KNOWN unresolved lookupd bugs in OSX that apple refuses to
    acknowledge and has failed to fix.

    currently there are temporary workarounds that eventually stop working
    because it's a BUG.

    However, here are some resources that have 'temporarily' worked for
    many, incl. me and they always stop working and have to be re-

    do a search for lookupd and you will see ALL THE FRIGGIN CRAP
    PROBLEMS of this bug that has existed since the beginning of OS X.

    to see the current lookupd configuration type this in the terminal:
    lookupd -configuration

    To fix it: In the Terminal (/Applications/Utilities/Terminal), do this
    (from the admin account):

    sudo mkdir /etc/lookupd
    sudo sh -c "echo TimeToLive 300 > /etc/lookupd/hosts"
    sudo sh -c "echo ValidateCache NO >> /etc/lookupd/hosts"

    You check to see if settings changed from time to time by:
    lookupd -configuration

    To partially fix the page load problem for safari, do this:
    defaults write WebKitInitialTimedLayoutDelay -float

    to see if settings of .25 are staying: enter this in terminal
    defaults read | grep WebKitInitialTimedLayoutDelay

    links/resources proof that is it a long-time bug and ongoing problem
    for both users & even in os x servers: (also
    has numerous links at the bottom of that page)

    still apple has failed to resolve fix explain or give a flying crap.
    hashmac, Aug 23, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.