Messages will still be printed to stderr if ypbind is started in debug mode.
- Don't exist if none of the servers listed in
/var/yp/binding/<domainname>.ypservers are reacheable. It's a temporary
failure that can be recovered from.
* cleanup for -Wall
* use __RCSID
the following were inspired by openbsd:
* only allow connections from reserved ports
* implement -insecure, which turns off the above restriction (required
for sunos 3.x and ultrix)
* prevent more than 100 domains from being bound at once, preventing
a denial of service attacks
This is a compromise between the Solaris 2.5 naming of this file
(/var/yp/binding/domain/ypservers and /var/yp/binding/domain/vers)
and traditional NetBSD naming (/var/yp/binding/domain.vers).
Changing to the Solaris naming makes the C library incompatible
with ypbind. While it's easy to change the C library, I don't feel
right about introducing a gratuitous incompatibility.
The current name (/var/yp/domain/ypservers) conflicts with the name
of the YP map listing slave servers for a domain.
Per discussion w/ Chris Demetriou and Luke Mewburn.
of YP servers a client should bind to, mostly verbatim, but slightly
modified for better semantics when nagging servers if a ypset has been
issued. Default to broadcast mode if no .ypservers file is present.
Documentation changes to match, slightly tweaked by Scott Reynolds and
myself.
Closes PR #1759.
- check malloc returns
- null terminate strncpy() strings
- use snprintf instead of sprintf
- pass the right arguments to the right functions
- check usage
- use err(3) and warn(3) instead of printfs.
ypbind; sleep 10; ypwhich
to fail (where failure is defined as ypwhich hangs until it gives up,
complaining about not being able to communicate with ypbind). Failure
mode pointed out by Chris G. Demetriou <cgd@cs.cmu.edu>.
is