summaryrefslogtreecommitdiffstats
path: root/libexec/ypxfr
Commit message (Collapse)AuthorAgeFilesLines
* Consistently set RPCGEN_CPP when running rpcgen, so the C preprocessordim2012-02-071-1/+1
| | | | | | set via ${CPP} is used, instead of always using hardcoded /usr/bin/cpp. MFC after: 1 week
* Fix the incompatible enum conversions in libexec/ypxfr in another, moredim2011-12-163-22/+24
| | | | | | | | messy way, so as to not disrupt other yp programs: just add casts to convert the incompatible enums, as the numerical values are the same (either by accident, design, or the phase of the moon at that time). MFC after: 1 week
* Revert r228592, as the non-messy way of fixing ypxfr breaks other ypdim2011-12-164-7/+8
| | | | | | | programs (e.g. usr.sbin/rpc.yppasswdd). Spotted by: np MFC after: 1 week
* Attempt to fix the numerous incompatible enum conversions indim2011-12-164-8/+7
| | | | | | libexec/ypxfr in the least disruptive way. MFC after: 1 week
* Fix incorrect usage of 'assure' and 'insure'.brucec2010-08-281-1/+1
| | | | Approved by: rrs (mentor)
* Fix typos and spelling mistakes.joel2010-08-061-1/+1
|
* Fix typo.joel2010-08-041-1/+1
|
* Make WARNS=6 the default for libexec/.ed2010-01-021-0/+3
| | | | | | | | | | | | | | | Just like bin/ and sbin/, I think setting WARNS to the highest value possible will make it more attractive for people to fix warnings. - The WARNS variable is set in the Makefile in the directory of the application itself, making it more likely that it will be removed out of curiosity to see what happens. - New applications will most likely build with WARNS=6 out of the box, because the author would more likely fix the warnings during development than lower WARNS. Unfortunately almost all apps in libexec require a lowered value of WARNS.
* Expand *n't contractions.ru2005-02-131-1/+1
|
* Remove definition of struct dom_binding, it's non-standard C code andstefanf2004-10-172-2/+0
| | | | unnecessary since src/include/rpcsvc/ypclnt.h's revision 1.10.
* Mechanically kill hard sentence breaks.ru2004-07-021-16/+30
|
* Don't pass a pointer to a 'long' to a function that expects an 'int *'.das2004-02-161-2/+2
| | | | | Submitted by: Roop Nanuwa <roop@hqst.com> PR: 62615
* Tidy up some xdrproc_t related warnings.peter2003-10-262-5/+7
|
* Use __FBSDID vs. rcsid[].obrien2003-05-045-20/+10
|
* english(4) police.schweikh2002-12-271-1/+1
|
* Uniformly refer to a file system as "file system".ru2002-12-121-1/+1
| | | | Approved by: re
* The .Nm utilitycharnier2002-07-061-5/+7
|
* Spell void * as void * rather than caddr_t. This is complicated by thedes2002-04-282-5/+5
| | | | | | fact that caddr_t is often misspelled as char *. Sponsored by: DARPA, NAI Labs
* Fix warnings.des2002-04-063-13/+13
| | | | Sponsored by: DARPA, NAI Labs
* ANSIfy and remove some dead code.des2002-02-066-53/+29
| | | | Sponsored by: DARPA, NAI Labs
* Apply the following mechanical transformations in preparation fordes2002-02-066-23/+23
| | | | | | | | | | | | | | | | | ansification and constification: s{\s+__P\((\(.*?\))\)}{$1}g; s{\(\s+}{\(}g; s{\s+\)}{\)}g; s{\s+,}{,}g; s{(\s+)(for|if|switch|while)\(}{$1$2 \(}g; s{return ([^\(].*?);}{return ($1);}g; s{([\w\)])([!=+/\*-]?=)([\w\(+-])}{$1 $2 $3}g; s{\s+$}{\n};g Also add $FreeBSD$ where needed. MFC after: 1 week
* Lock down with WFORMAT?=1, with overrides in the subdirectories whichkris2002-02-041-0/+1
| | | | are not yet warning-clean. Tested on i386 and alpha.
* yp(4) -> yp(8).ru2002-01-141-1/+1
| | | | PR: docs/30797
* yp_errno is an `enum ypstat`.dd2001-07-241-1/+1
| | | | | | PR: 29190 Submitted by: Cristan Szmajda <cristan@unsw.edu.au> Reviewed by: md5(1)
* - Backout botched attempt to intoduce MANSECT feature.ru2001-03-261-0/+2
| | | | - MAN[1-9] -> MAN.
* change callrpc() from taking "char *" args, I'm quite sure they really meantalfred2001-03-231-1/+0
| | | | | | to use "void *". remove a duplicate prototype for callrpc() from libexec/ypxfr/ypxfr_extern.h
* Set the default manual section for libexec/ to 8.ru2001-03-201-2/+0
|
* Prepare for mdoc(7)NG.ru2001-01-161-1/+1
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-1/+1
|
* Use Fx macro wherever possible.ru2000-11-141-1/+1
|
* Spelling fix: transfered --> transferredjlemon2000-06-021-1/+1
| | | | Submitted by: dan@dan.emsphone.com
* Fix various man pages to stop abusing the .Bx macro to generate thempp2000-01-231-8/+9
| | | | string "FreeBSD". Use the .Fx macro instead.
* $Id$ -> $FreeBSD$peter1999-08-288-8/+8
|
* Fix ypxfr so that it can be run from cron.wpaul1999-05-101-4/+4
| | | | Patch submitted by: Dan Nelson <dnelson@emsphone.com>
* Fixed printf format errors.bde1998-08-021-2/+2
|
* Fixed missing dependencies on headers generated by rpcgen, as usual.bde1998-05-101-8/+10
| | | | | Removed bogus dependencies of generated .c files on generated headers. Sorted sources lists.
* .Sh AUTHOR -> .Sh AUTHORS. Use .An/.Aq.charnier1998-03-191-2/+2
|
* Use full path in synopsis. Sort #includes. Use .Tn for NIS.charnier1997-12-086-104/+163
|
* Putting records with zero-length keys into a Berkeley DB hash databasewpaul1997-09-301-6/+22
| | | | | | | | | | | | | | | | | is asking for trouble (sequential database enumerations can get caught in an infinite loop). The yp_mkdb(8) utility avoids putting such records into a database, but ypxfr does not. Today I got bit by a NULL entry in one of the amd maps on my network, which is served by a SunOS master. The map was transfered successfully to my FreeBSD slave, but attempting to dump it with ypcat(1) caused ypserv(8) to transmit the same record over and over again, making the map appear to be infinitely large. I finally noticed the problem while testing a new version of amd under development at the Columbia CS department, which began gobbling up insane amounts of memory while trying to swallow the map. To deal with this problem, I'm modifying ypxfr to watch for records with zero-length keys and turn them into something less destructive before writing them to the database.
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-281-3/+3
| | | | posix standard on the topic.
* Revert $FreeBSD$ to $Id$peter1997-02-228-13/+13
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-148-13/+13
| | | | | | | | 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.
* Sort cross references.wosch1997-01-131-3/+3
|
* Change declaration of yp_errno from int to enum ypstat so that itwpaul1996-12-231-2/+3
| | | | | | | matches what's in ypserv/yp_extern.h (which I changed when I added the async DNS stuff). The conflict broke the build of rpc.yppasswdd. Pointed out by: bde
* Give ypxfr the ability to detect the presence of the YP_INTERDOMAINwpaul1996-10-254-7/+91
| | | | | | | | | and YP_SECURE flags so that it can properly add them to newly created maps when needed. This applies only when using the 'standard' method for map transfers. When using rpc.ypxfrd, the whole map is copied verbatim, along with any special entries that may be encoded in it. Also made -Wall a little quieter for ypxfrd_getmap.c.
* Add a couple of reserved port checks: don't talk to either ypservwpaul1996-10-201-5/+24
| | | | | | | | or rpc.ypxfrd processes on remote systems that aren't bound to reserved ports. The servers already do reserved port checks on the clients. Obtained from: scrutinizing the OpenBSD ypxfr sources. (Note that this applies to the ypserv check only; OpenBSD doesn't have an rpc.ypxfrd.)
* Fixed DPADD.bde1996-09-051-2/+3
|
* Fill in new arguments in the ypxfr_getmap structure (byte order,wpaul1996-07-041-2/+16
| | | | | db type, filename) and check for new failure codes (db mismatch, endian mismatch).
* Take ypxfrd_xdr.c out of SRCS line. It should be included in librpcsvc,wpaul1996-06-061-2/+2
| | | | | | | | | which ypxfr links with. (Sorry: left over development bogon.) Just a reminder: you must rebuild librpcsvc before you build this program. Pointed out by: Stephen Hocking
* Add support for rpc.ypxfrd and document it in the man page.wpaul1996-06-058-40/+230
| | | | | | | | Also generallize the yp_dbwrite functions a little: allow the caller to specify certain flags. I need this mostly for some changes to rpc.yppasswdd to allow in-place updates. Also change Makefile a little to use the same format as ypserv.
OpenPOWER on IntegriCloud