Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by krbdev.mit.edu (8.9.3p2) with ESMTP id NAA01435; Tue, 2 Nov 2004 13:06:45 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id iA2I6jDc002931; Tue, 2 Nov 2004 13:06:45 -0500 (EST)
Received: from [18.101.0.226] ([18.101.0.226]) (authenticated bits=0) (User authenticated as raeburn@ATHENA.MIT.EDU) by outgoing.mit.edu (8.12.4/8.12.4) with ESMTP id iA2I6h1U012133 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Tue, 2 Nov 2004 13:06:44 -0500 (EST)
In-Reply-To: <rt-2758-12297.17.3585813490622@krbdev.mit.edu>
References: <rt-2758-12297.17.3585813490622@krbdev.mit.edu>
MIME-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F39DD1C8-2CF9-11D9-8DA2-000A95909EE2@mit.edu>
Content-Transfer-Encoding: 7bit
Cc: Ken Raeburn <raeburn@mit.edu>, krb5-prs@mit.edu
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: [krbdev.mit.edu #2758] yarrow locking broken on 1.4 branch
Date: Tue, 2 Nov 2004 13:06:42 -0500
To: rt-comment@krbdev.mit.edu
X-Mailer: Apple Mail (2.619)
X-Scanned-BY: MIMEDefang 2.42
RT-Send-Cc: 
X-RT-Original-Encoding: us-ascii
Content-Length: 192

On Nov 2, 2004, at 10:41, Sam Hartman via RT wrote:

> Where do you end up doing the fork check then?

There's still a check before generating output.  That should be enough, 
shouldn't it?