Date: Fri, 15 Jun 2001 06:53:27 -0700 (PDT) From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: Re: tcsh.cat Message-ID: <200106151353.f5FDrRw95049@bunrab.catwhisker.org> In-Reply-To: <Pine.BSF.4.21.0106152325320.84795-100000@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>Date: Fri, 15 Jun 2001 23:33:07 +1000 (EST) >From: Bruce Evans <bde@zeta.org.au> >> I have heard on several occasions of peope using symlink(2) to >> atomically store some small piece of information for locking purposes. >> (Symlink was more reliably atomic over NFS than other methods.) So it >> is possible that changing this might break something. >Yes. /etc/malloc.conf is another example (for non-locking purposes). And another: dhcp-133[1] ls -l .netscape/lock lrwxrwxr-x 1 david wheel 13 Jun 15 06:40 .netscape/lock -> 1.0.0.127:612 :-}, david (making no claims about what is "good practice", here) -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106151353.f5FDrRw95049>