On Mon, Apr 28, 2003 at 10:48:28AM +0200, Fabio Massimo Di Nitto [EMAIL
PROTECTED] wrote:
Package: mozilla-browser
Version: 2:1.3-4
Severity: important
Hi all,
the problem is farly simple. open mozilla. access the server.
change the ip/dns entry on server. reaccess the server.
Mike Hommey wrote:
On Mon, Apr 28, 2003 at 10:48:28AM +0200, Fabio Massimo Di Nitto [EMAIL
PROTECTED] wrote:
Package: mozilla-browser
Version: 2:1.3-4
Severity: important
Hi all,
the problem is farly simple. open mozilla. access the server.
change the ip/dns entry on server.
On Sun, Apr 29, 2007 at 12:06:59PM +0200, Mike Hommey wrote:
Were you by any chance using nscd ?
I do not remember. And the environment where I spotted this bug does not
exist anymore.
Regards
Artur
--
(ac) ,
_รณ_ We all live in a
On Sun, Apr 29, 2007 at 02:23:31PM +0200, Fabio Massimo Di Nitto [EMAIL
PROTECTED] wrote:
Mike Hommey wrote:
On Mon, Apr 28, 2003 at 10:48:28AM +0200, Fabio Massimo Di Nitto [EMAIL
PROTECTED] wrote:
Package: mozilla-browser
Version: 2:1.3-4
Severity: important
Hi all,
the
Mike Hommey wrote:
Okay, I could reproduce half of the problem, but things evolved a few
months after you filed your bug, according to upstream CVS.
They changed their DNS service so that it would only cache DNS entries
for 60 seconds (which you can change if you set the
On Sun, Apr 29, 2007 at 05:07:25PM +0200, Fabio Massimo Di Nitto wrote:
Mike Hommey wrote:
I think this is enough for this bug to be closed. If not, I could set
these 2 preferences to 0 to disable DNS caching.
Go ahead and close it.
Seconded :)
--
http://www.last.fm/user/arturcz/
--
To
6 matches
Mail list logo
