From owner-freebsd-hackers Fri Nov 5 2:39:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id F2BD714D98 for ; Fri, 5 Nov 1999 02:39:21 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id LAA28782 for ; Fri, 5 Nov 1999 11:39:15 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma028742; Fri, 5 Nov 99 11:39:16 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id LAA01860 for ; Fri, 5 Nov 1999 11:39:09 +0100 (MET) Received: (qmail 5037 invoked by uid 666); 5 Nov 1999 10:39:29 -0000 Date: Fri, 5 Nov 1999 11:39:29 +0100 From: Jos Backus To: Sheldon Hearn Cc: Jos Backus , freebsd-hackers@freebsd.org Subject: Re: ftpd feature: lock file being stored Message-ID: <19991105113929.B2328@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19991105111518.A2328@hal.mpn.cp.philips.com> <7173.941797101@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <7173.941797101@axl.noc.iafrica.com>; from sheldonh@uunet.co.za on Fri, Nov 05, 1999 at 12:18:21PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 05, 1999 at 12:18:21PM +0200, Sheldon Hearn wrote: > Then use fstat. :-) OK, OK :) > I think you've developed a complex solution to a more simply solved > problem. UNIX offers you lots of little tools for good reason. Adding > functionality to ftpd that is available through other tools doesn't seem > wise to me. I'm not yet convinced that your solution does what I want in a reliable fashion. > What does "polling the directory" mean? Scanning the directory for new files, as the aforementioned script does. If you have more than one script doing this at the same time, both may conclude that a given file is ``available'' and try to act upon it. Inevitably, one of those scripts will fail. Hence my solution. But maybe I don't quite understand the problem :-) (Yes, I know you will say, "Don't run more than one script at a time then.". But whether this is possible really depends on the application and moreover seems to be an unecessary restriction.) Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message