summaryrefslogtreecommitdiffstats
path: root/usr.sbin/rpc.lockd
Commit message (Collapse)AuthorAgeFilesLines
* Perform a major cleanup of the usr.sbin Makefiles.obrien2001-07-201-2/+2
| | | | | These are not perfectly in agreement with each other style-wise, but they are orders of orders of magnitude more consistent style-wise than before.
* Distinguish between rpc version numbers in the client cache to avoidalfred2001-04-281-1/+6
| | | | replying on the wrong port.
* handles.c belonged to the old stub lockd, nuke it.alfred2001-04-281-61/+0
|
* procs.c belonged to the old stub lockd, nuke it.alfred2001-04-281-592/+0
|
* mdoc(7) police: Removed forgotten .Pp.ru2001-04-271-1/+0
|
* Fix compiling without -O, some dead code was using non-existant functions,alfred2001-04-252-6/+10
| | | | | | | | | | | make the code not automatically dead but actually use the debug level in order to determine if output is needed. Fix non-existant from_addr() by #define'ing it to inet_ntoa(). Remove hardcoded -g from Makefile. Reported by: "John W. De Boskey" <jwd@bsdwins.com> Tested by: "John W. De Boskey" <jwd@bsdwins.com>
* Remove section from bugs that says we don't support client locks.alfred2001-04-191-11/+0
| | | | Pointed out by: Martin Blapp <mb@imp.ch>
* remove debug code left in by accidentalfred2001-04-181-7/+0
|
* Implement client side NFS locks.alfred2001-04-176-9/+672
| | | | | Obtained from: BSD/os Import Ok'd by: mckusick, jkh, motd on builder.freebsd.org
* - Backout botched attempt to introduce MANSECT feature.ru2001-03-261-0/+1
| | | | - MAN[1-9] -> MAN.
* Set the default manual section for usr.sbin/ to 8.ru2001-03-201-1/+0
|
* Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) andalfred2001-03-198-160/+2390
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | associated changes that had to happen to make this possible as well as bugs fixed along the way. Bring in required TLI library routines to support this. Since we don't support TLI we've essentially copied what NetBSD has done, adding a thin layer to emulate direct the TLI calls into BSD socket calls. This is mostly from Sun's tirpc release that was made in 1994, however some fixes were backported from the 1999 release (supposedly only made available after this porting effort was underway). The submitter has agreed to continue on and bring us up to the 1999 release. Several key features are introduced with this update: Client calls are thread safe. (1999 code has server side thread safe) Updated, a more modern interface. Many userland updates were done to bring the code up to par with the recent RPC API. There is an update to the pthreads library, a function pthread_main_np() was added to emulate a function of Sun's threads library. While we're at it, bring in NetBSD's lockd, it's been far too long of a wait. New rpcbind(8) replaces portmap(8) (supporting communication over an authenticated Unix-domain socket, and by default only allowing set and unset requests over that channel). It's much more secure than the old portmapper. Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded to support TI-RPC and to support IPV6. Umount(8) is also fixed to unmount pathnames longer than 80 chars, which are currently truncated by the Kernel statfs structure. Submitted by: Martin Blapp <mb@imp.ch> Manpage review: ru Secure RPC implemented by: wpaul
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-1/+1
|
* Use Fx macro wherever possible.ru2000-11-141-2/+2
|
* Don't call syslog() without a format string.kris2000-07-121-1/+1
|
* $Id$ -> $FreeBSD$peter1999-08-286-6/+6
|
* Add $Id$, to make it simpler for members of the translation teams tonik1999-07-121-0/+1
| | | | | | | | | | | | | | | | | track. The Id line is normally at the bottom of the main comment block in the man page, separated from the rest of the manpage by an empty comment, like so; .\" $Id$ .\" If the immediately preceding comment is a @(#) format ID marker than the the $Id$ will line up underneath it with no intervening blank lines. Otherwise, an additional blank line is inserted. Approved by: bde
* Removed bogus dependencies of generated .c files on generated headers.bde1998-05-101-2/+2
|
* Fixed `make -jN' for large N, as usual.bde1998-03-061-2/+2
|
* Use err(3). Add usage() and #includes.charnier1997-10-135-52/+58
|
* Typo fix: ${.DESTDIR} -> ${DESTDIR}.asami1997-05-231-2/+2
| | | | Reviewed by: bde
* Fixed type mismatch caused by bogus prototypes. rpcgen for some reasonbde1997-04-151-2/+2
| | | | doesn't generate any prototypes for the functions to be registered.
* Typo police.mpp1997-03-161-2/+2
| | | | Partially obtained from: NetBSD PR# 3333
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
* Sort cross references.wosch1997-01-201-2/+2
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | 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.
* rpc.rstatd -> rpc.lockd typopeter1996-08-161-1/+1
| | | | Noticed by: tholo@sigmasoft.com (Thorsten Lockert)
* Correct the rpc.lockd and rpc.statd man pages to not referencempp1996-04-071-3/+3
| | | | | | 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.
* Tweaks for the stub lockd.peter1996-04-016-242/+46
| | | | | | | - 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
* Import Jan 15 version of Andrew Gordon <andrew.gordon@net-tel.co.uk>'speter1996-02-177-0/+1481
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.
OpenPOWER on IntegriCloud