Mon Nov 12 13:15:33 PST 2012
- Previous message: [Slony1-general] replication fails to due bad DNS at startup, requires slony restart to fix
- Next message: [Slony1-general] replication fails to due bad DNS at startup, requires slony restart to fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Nov 12, 2012 at 04:05:37PM -0500, Christopher Browne wrote: > Is it possible that your libc is doing cacheing? If *that's* the > case, and I'm suspicious of it, then you really would need to restart > the slon to get "unstuck" from what libc has cached on you... More likely, the system resolver is pointing at a caching name server. Best, A -- Andrew Sullivan ajs at crankycanuck.ca
- Previous message: [Slony1-general] replication fails to due bad DNS at startup, requires slony restart to fix
- Next message: [Slony1-general] replication fails to due bad DNS at startup, requires slony restart to fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list