Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!rbj
From: rbj@uunet.UU.NET (Root Boy Jim)
Newsgroups: comp.lang.perl
Subject: Re: While learning PERL... a suggestion
Keywords: perl file learn suggest
Message-ID: <119542@uunet.UU.NET>
Date: 22 Jan 91 20:19:50 GMT
References: <1991Jan21.214453.25039@convex.com> <119440@uunet.UU.NET> <1991Jan22.054732.14797@convex.com>
Organization: UUNET Communications Services, Falls Church, VA
Lines: 32

In article <1991Jan22.054732.14797@convex.com> tchrist@convex.COM (Tom Christiansen) writes:
>From the keyboard of rbj@uunet.UU.NET (Root Boy Jim):
>:>:Another thing perl needs is the ability to create lock files. Sysopen?
>
>With NFS, all bets are off: the same file may be created and deleted
>more than once, with success returned to both.  It's horrid, I know, but
>it's there.  Too many of us use NFS to rely on this.

NFS? Did *I* say NFS? I think not!
What I am trying to do is steal one of UUCP's dialout modems,
following the same protocol that tip/cu use.

Perhaps you are correct, that it won't work on across NFS.
The solution is not to attempt it then, but only to use it
on local filesystems. We don't rip all that other stuff
out of the kernel because of NFS's braindamage.

>Anyway aren't you "supposed" to use link, not creat, for creating
>lock files of this nature?

Not, I believe, since the "new" flags were added to open.

>I'm not saying we really don't need a sysopen -- some other flags
>(like NDELAY) might be nice.  Just that for locking this isn't really
>great.  If you have syscall(), you could probably put something
>together without code changes.

Yes, I'l do just that.
-- 

	Root Boy Jim Cottrell <rbj@uunet.uu.net>
	Close the gap of the dark year in between