#
259065 |
|
07-Dec-2013 |
gjb |
- Copy stable/10 (r259064) to releng/10.0 as part of the 10.0-RELEASE cycle. - Update __FreeBSD_version [1] - Set branch name to -RC1
[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so start releng/10.0 at '100' so the branch is started with a value ending in zero.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
249583 |
|
17-Apr-2013 |
gabor |
- Correct mispellings of the word necessary
Submitted by: Christoph Mallon <christoph.mallon@gmx.de> (via private mail)
|
#
114629 |
|
04-May-2003 |
obrien |
Use __FBSDID vs. rcsid[].
|
#
81586 |
|
13-Aug-2001 |
ru |
Removed duplicate VCS ID tags, as per style(9).
|
#
50473 |
|
27-Aug-1999 |
peter |
$Id$ -> $FreeBSD$
|
#
32553 |
|
16-Jan-1998 |
bde |
Removed redundant declarations. rpcgen generates `typedef enum foo;' from `enum foo;'.
|
#
26208 |
|
28-May-1997 |
wpaul |
Resolve conflicts.
|
#
23037 |
|
23-Feb-1997 |
peter |
Revert $FreeBSD$ to $Id$
|
#
21673 |
|
14-Jan-1997 |
jkh |
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.
|
#
16957 |
|
04-Jul-1996 |
wpaul |
There are a few small additions to the protocol to make it easier to use in mixed environments:
- Add three new members to the request structure:
- a filename specification - a database type specification - a system byte prder specification
These allow the client to ask the server for a particular type of database (Berkeley DB hash/btree/recno, GNU GDBM, dbm, ndbm, etc...) and get back a meaningful error if the server doesn't support it. The byte order spec is needed if the database type is byte order sensntive. You don't, for example, want to read an ndbm database from a big endian machine on a little endian machine (the ndbm code will explode). The filename spec lets the client handle things like ndbm which uses two seperate files per database (foo.dir and foo.pag). The client can ask for each half, one at a time.
- Add a list of database types and byte order values. Each list has a wildcard 'ANY' entry which lets the client ask for whatever the server supports. (XFR_ENDIAN_ANY is useful with the Berkeley DB hash method for instance, since it isn't byte order sensitive.)
- Add two newserver failure codes: XFR_DB_TYPE_MISMATCH and XFR_DB_ENDIAN_MISMATCH. The server uses these to tell the client that it doesn't support the requested type/byte order.
These changes were made at the suggestion of Thorsten Kukuk, the current maintainer of the Linux ypserv distribution. This allows Linux and FreeBSD NIS servers to use the same ypxfrd protocol and avoid accidentally exchanging incompatible map files.
|
#
16120 |
|
05-Jun-1996 |
wpaul |
This commit was generated by cvs2svn to compensate for changes in r16119, which included commits to RCS files with non-trunk default branches.
|
#
16119 |
|
05-Jun-1996 |
wpaul |
(I hope I'm doing this correctly.)
Import a my own little ypxfrd protocol. Note that this protocol is _NOT_ the same as Sun's, which is proprietary.
This basically impliments an RPC-based file transfer protocol which lets a slave server suck over a raw map database file from the master. This is many times faster than the normal method, which requires reading the records from ypserv via yp_all() and then creating a new database on the fly, particularly when you have many tens of thousands of records in a map (e.g. a huge passwd database).
The protocol number I chose falls within the 'user-specified' range. Maybe we should register it with Sun so we can get an official vendor number for it. :)
|