From owner-freebsd-current Thu May 30 9:52:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by hub.freebsd.org (Postfix) with ESMTP id B57CE37B407 for ; Thu, 30 May 2002 09:52:49 -0700 (PDT) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id A9A333198DC; Thu, 30 May 2002 11:52:51 -0500 (CDT) Date: Thu, 30 May 2002 11:52:51 -0500 From: "David W. Chapman Jr." To: current@freebsd.org Subject: FW: Re: Error with post 1.1 release Postfix and Cyrus -Possible Bug in VM system Message-ID: <20020530165251.GB1018@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.99i X-Operating-System: FreeBSD 4.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Do we have anyone working on the VM system that could look at this? ----- Forwarded message from Wietse Venema ----- Date: Thu, 30 May 2002 12:49:10 -0400 (EDT) Reply-To: Postfix users From: wietse@porcupine.org (Wietse Venema) To: Postfix users Subject: Re: Error with post 1.1 release Postfix and Cyrus X-Mailer: ELM [version 2.4ME+ PL82 (25)] Sender: owner-postfix-users@postfix.org You're somehow still running qmgr code that speaks the protocol from before 20020514. To find the file, # find / \( -name qmgr -o -name nqmgr \) -ls But you may not find this file. After upgrading Postfix I very, very, occasionally find that FreeBSD will execute a new process from an old file that was just replaced. Postfix always installs executables by using "mv newfile oldfile". At this time, the old file may still be executing, and the parent process is always executing (the Postfix master daemon). I suspect an obscure VM system bug. "postfix reload" does not seem to cure this condition. The problem goes away after "postfix stop" then "postfix start", which terminates the parent process. This has happened to me only twice over the past year. My server and workstations run FreeBSD versions 4.1 - 4.4. I haven't found the time and energy to debug this. Wietse - To unsubscribe, send mail to majordomo@postfix.org with content (not subject): unsubscribe postfix-users ----- End forwarded message ----- -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message