head	1.3;
access;
symbols
	r19960115:1.1.1.1
	A_GORDON:1.1.1;
locks; strict;
comment	@# @;


1.3
date	96.04.02.01.41.44;	author peter;	state dead;
branches;
next	1.2;

1.2
date	96.04.01.05.29.57;	author peter;	state Exp;
branches;
next	1.1;

1.1
date	96.02.17.15.11.28;	author peter;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	96.02.17.15.11.28;	author peter;	state Exp;
branches;
next	;


desc
@@


1.3
log
@Move rpc.statd and rpc.lockd to usr.sbin via repository copy as per
discussionn when they were initially added some time ago.
These programs are not needed before nfs is up and running to possibly
mount /usr so they dont need to be static and on the root fs.
@
text
@#	$Id: Makefile,v 1.2 1996/04/01 05:29:57 peter Exp peter $

PROG =	rpc.lockd
SRCS =	nlm_prot_svc.c lockd.c procs.c
MAN8 =	rpc.lockd.8

DPADD=	${LIBRPCSVC}
LDADD=	-lrpcsvc

CFLAGS+= -I.

CLEANFILES= nlm_prot_svc.c nlm_prot.h

RPCSRC= ${.DESTDIR}/usr/include/rpcsvc/nlm_prot.x
RPCGEN= rpcgen -L -C

nlm_prot_svc.c: ${RPCSRC} nlm_prot.h
	${RPCGEN} -m -o ${.TARGET} ${RPCSRC}

nlm_prot.h: ${RPCSRC}
	${RPCGEN} -h -o ${.TARGET} ${RPCSRC}

test: test.c
	cc -o test test.c -lrpcsvc

.include <bsd.prog.mk>
@


1.2
log
@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
@
text
@d1 1
a1 1
#	$Id: Makefile,v 1.1.1.1 1996/02/17 15:11:28 peter Exp $
@


1.1
log
@Initial revision
@
text
@d1 1
a1 1
#	$Id$
d4 1
a4 1
SRCS =	lockd.c procs.c
d10 12
a21 1
.include <bsd.prog.mk>
d26 1
@


1.1.1.1
log
@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.
@
text
@@
