Search Again: Re: 2.2.1 Lockup From: Simon Forster Date: Friday, July 6, 2001 Time: 4:00:53 am on 6/7/01 10:57 am, Sigurdur Ragnarsson at siggi@menandmice.com wrote: > In some cases, QuickDNS 2.2.1 doesn't correctly detect failed zone transfer > requests and believes a zone transfer is in progress although it has been > aborted. When you Quit QuickDNS it waits until all zone transfers finish, but > when a 'zombie' zone transfer is in progress, QuickDNS will wait forever > appearing to be locked and a force-quit is needed to terminate the > application. > > This problem has been solved in QuickDNS 3.5. Thank you for that - I thought that no answer would be forthcoming. I have a (remote) server which QuickDNS is locking on quit. This server acts as a secondary pulling data from another (local) copy of QDNS. The local copy of QDNS locking up presents no big problems as I can perform percussive maintenance as required. However, I need to fix the remote server... <sigh> ...how much an upgrade? Simon Forster ________________________________________________ LDML Ltd, 4/5 Hazlitt Mews, London, W14 0JZ, UK <tel int="+44 20 7602 9370" uk="020 7602 9370"> <fax int="+44 20 7371 6662" uk="020 7371 6662"> <mailto:simon@ldml.com> ________________________________________________

Messages In This Thread: 2.2.1 Lockup by Simon Forster on Jul 5, 2001 at 12:20:33 am Re: 2.2.1 Lockup by Sigurdur Ragnarsson on Jul 6, 2001 at 2:58:41 am Re: 2.2.1 Lockup by Simon Forster on Jul 6, 2001 at 4:00:53 am Re: 2.2.1 Lockup by Simon Forster on Jul 6, 2001 at 5:00:44 am Re: 2.2.1 Lockup by Sigurdur Ragnarsson on Jul 6, 2001 at 8:19:21 am Re: 2.2.1 Lockup by Simon Forster on Jul 6, 2001 at 9:55:23 am