From owner-freebsd-questions Mon Dec 13 2: 1:31 1999 Delivered-To: freebsd-questions@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 9AA8114CA3 for ; Mon, 13 Dec 1999 02:01:27 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11xSHt-0007Lw-00; Mon, 13 Dec 1999 12:01:01 +0200 From: Sheldon Hearn To: "Artem Koutchine" Cc: questions@FreeBSD.ORG Subject: Re: questions about file locking and memory usage In-reply-to: Your message of "Sun, 12 Dec 1999 20:05:10 +0300." <000501bf44c3$15e05c80$0100a8c0@m1> Date: Mon, 13 Dec 1999 12:01:00 +0200 Message-ID: <28267.945079260@axl.noc.iafrica.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 12 Dec 1999 20:05:10 +0300, "Artem Koutchine" wrote: > 1) Memory usage by programs > > C source : > main () { > while(1); > } > > as you see, it does nothing, nor it uses any libraries. ust an > empty look. Wrong. The default for cc in FreeBSD is to link against some standard libraries. Try the -nostdlib option to cc. > 2) How do i lock file reliably w/o depending whether it is on local > FS or NFS. > > flock does not work on NFS as i know, .lock locking made in a > normal simple way does not work either. What wouold be the > corrent and reliable way? Anything you do here will end up being homebrew. Locking is a known bugbear with NFS. > 3) Code sharing > When i am runnning 15 perl scripts i am sure that some part > of code is shared among them Yes, probably the text segment of the perl interpreter. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message