Xref: utzoo comp.unix.admin:274 comp.unix.internals:460
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!princeton!narnia.Princeton.EDU!lemke
From: lemke@Princeton.EDU (Kennedy Lemke)
Newsgroups: comp.unix.admin,comp.unix.internals
Subject: flock and rpc.lockd
Message-ID: <3005@idunno.Princeton.EDU>
Date: 2 Oct 90 20:31:06 GMT
Sender: news@idunno.Princeton.EDU
Reply-To: Kennedy_J_Lemke@Princeton.EDU
Followup-To: comp.unix.admin
Organization: Princeton University
Lines: 22

Question: On a Sun 4/390 running SunOS 4.0.3, if rpc.lockd is
killed (or, rather, not running), would that cause the following
c code:

	flock(fileno(st), LOCK_SH|LOCK_NB);

to set errno to 79?  (Or, more specifically, as the man page indicates,
when rpc.lockd is not running, is it then the case that the number
of simultaneous file and record locks is decreased or becomes zero?
If so, does this then ultimately have the effect that no file locking
is therefore done on the system?

Please email me since I can't read this group as often as I'd like to.
Thanks.
				Kennedy Lemke
				Systems Programmer
				CIT--87 Prospect
				Princeton University

Work Phone: (609) 258-6033      Internet: lemke@Princeton.EDU
Fax Phone:  (609) 258-3943      uucp:     ...rutgers!princeton!lemke
Home Phone: (609) 275-7298      Bitnet:   LEMKE@PUCC.BITNET