Thanks, Michele! Even though the ping isn't particularly slow, adding the
entry to /etc/hosts does the trick for the web2py startup.
I'm still thinking that lookups might be slow for all sorts of reasons, and
the following bunch of lines should perhaps be moved from console()
into web2pyDialog.
try the following on the command line:
$ ping $(hostname -f)
if it takes long time and then it says something like "unkwown host" that
your machine has a name that is neither resolvable by dns nor by /etc/hosts
lookup. To fix the problem try to add the following line in your
/etc/hosts:
127.0.0.
...and guess what what: I've been working on my first web2py project since
almost three month, and thought this was normal! (I hear you laughing.)
Until yesterday when I had my WLAN turned off and web2py launched almost
instantly.
I couldn't believe it, launched the debugger, and traced the pro
3 matches
Mail list logo
