Commit Graph

13 Commits

Author SHA1 Message Date
bde
5a9e814a5d Removed bogus dependencies of generated .c files on generated headers. 1998-05-10 16:03:17 +00:00
bde
9fa4e2234d Fixed `make -jN' for large N, as usual. 1998-03-06 14:34:47 +00:00
charnier
459d0ae253 Use err(3). Add usage() and #includes. 1997-10-13 11:13:33 +00:00
asami
21b8549c72 Typo fix: ${.DESTDIR} -> ${DESTDIR}.
Reviewed by:	bde
1997-05-23 08:43:27 +00:00
bde
637b655086 Fixed type mismatch caused by bogus prototypes. rpcgen for some reason
doesn't generate any prototypes for the functions to be registered.
1997-04-15 16:18:57 +00:00
mpp
d60f3d1d85 Typo police.
Partially obtained from: NetBSD PR# 3333
1997-03-16 07:12:20 +00:00
peter
32d6b795de Revert $FreeBSD$ to $Id$ 1997-02-22 16:15:28 +00:00
wosch
00e37028d0 Sort cross references. 1997-01-20 00:03:00 +00:00
jkh
9c0cd3f9df Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.

Boy, I'm glad we're not using sup anymore.  This update would have been
insane otherwise.
1997-01-14 07:20:47 +00:00
peter
d470b3a5fe rpc.rstatd -> rpc.lockd typo
Noticed by: tholo@sigmasoft.com (Thorsten Lockert)
1996-08-16 09:44:40 +00:00
mpp
dbfb32fa91 Correct the rpc.lockd and rpc.statd man pages to not reference
their path names in the synopsis line (especially since they
referenced the wrong path!).  Corrected some other minor problems
with the rpc.lockd man page.
1996-04-07 08:55:32 +00:00
peter
62fac34fe1 Tweaks for the stub lockd.
- Use rpcgen to generate the unmodified boilerplate code rather than
  having it in the repository.
- Eliminate the conflicting function names by changing them to their
  "natural" rpcgen generated names
1996-04-01 05:30:04 +00:00
peter
2db8f15200 Import Jan 15 version of Andrew Gordon <andrew.gordon@net-tel.co.uk>'s
stub lockd.

This implements just the protocol, but does not interact with the kernel.
It says "Yes!" to all requests.  This is useful if you have people using
tools that do locking for no reason (eg: some PC NFS systems running some
Microsoft products) and will happily report they couldn't lock the file
and merrily proceed anyway.  Running this will not change the reliability of
sharing files, it'll just keep it out of everybody's face.
1996-02-17 15:11:29 +00:00