Man pages › Compared with Linux and the BSDs

`ypmatch(1)` on Solnix vs Linux and the BSDs

On Solnix, ypmatch is the illumos ypmatch at /usr/bin/ypmatch. It takes the same four options as FreeBSD and OpenBSD (-d, -k, -t, -x). NetBSD adds -b and -z, which Solnix does not document.

The manual pages

Solnix: ypmatch(1) from pkgs.solnix.illumos-world-man · illumos.org
FreeBSD: ypmatch(1) 15.1-RELEASE
OpenBSD: ypmatch(1) 8.0
NetBSD: ypmatch(1) 11.0

What Solnix runs

A default Solnix system runs the illumos ypmatch at /usr/bin/ypmatch, published in pkgs.solnix.illumos-world-man. No other variants are shipped.

Differences

Compared with	Topic	What differs
NetBSD	`-z` (trailing NUL in key)	NetBSD ypmatch `-z` appends a NUL to the key before the lookup, for mail.aliases maps. The Solnix page has no `-z`, so such lookups are not documented on Solnix. Source: NetBSD ypmatch(1) -z; Solnix ypmatch(1) SYNOPSIS and OPTIONS
NetBSD	`-b` (bind retries)	NetBSD ypmatch `-b` num_retry limits how many times it retries reaching the ypserver, in the range 0 to 65535. The Solnix page has no `-b` and does not say how long it waits for a server. Source: NetBSD ypmatch(1) -b; Solnix ypmatch(1) OPTIONS
FreeBSD	`-k` output format	Solnix ypmatch `-k` prints the key followed by a colon before the value. The FreeBSD page says only 'Display map keys' and does not document the colon. Source: Solnix ypmatch(1) -k; FreeBSD ypmatch(1) -k
OpenBSD, NetBSD	`-k` output format	Solnix, OpenBSD and NetBSD all document `-k` as printing the key followed by a colon before the value. Solnix does not repeat the BSD note that it helps when values are null. Source: Solnix ypmatch(1) -k; OpenBSD ypmatch(1) -k; NetBSD ypmatch(1) -k
NetBSD	nickname table source	NetBSD ypmatch `-x` reads `/var/yp/nicknames` and falls back to a built-in table if the file is missing. The Solnix page says `-x` lists the nicknames the command knows and their map names, and names no file. Source: NetBSD ypmatch(1) -x; Solnix ypmatch(1) -x
FreeBSD, OpenBSD, NetBSD	key matching rules	Solnix documents that keys must be the same case and length, that no pattern matching is available, and that an unmatched key produces a diagnostic. The three BSD pages do not say this. Source: Solnix ypmatch(1) DESCRIPTION; FreeBSD, OpenBSD and NetBSD ypmatch(1) DESCRIPTION
FreeBSD, OpenBSD, NetBSD	exit status and file descriptors	Solnix documents exit 0 on success and 1 on error. It also notes an RPC error if too few file descriptors are available. The BSD pages have no EXIT STATUS or NOTES section for this. Source: Solnix ypmatch(1) EXIT STATUS, NOTES; FreeBSD, OpenBSD and NetBSD ypmatch(1)
Linux	no Linux counterpart in bundle	The bundle has no Linux ypmatch page, so no Linux comparison can be made. The manual does not say how Linux behaves. Source: Bundle header (counterparts: freebsd, openbsd, netbsd only)

Standards

POSIX: ypmatch is not a POSIX.1-2024 utility.
Solnix: The Solnix page has no ATTRIBUTES or INTERFACE STABILITY section in the bundle, but its SEE ALSO lists attributes(7).

Writing portable scripts

Use only -d, -k, -t and -x in scripts: all four systems document them. Avoid NetBSD's -b and -z.
Do not rely on the exact -k output format on FreeBSD, whose page does not document the colon.

Every difference here is taken from the manual pages linked above: Solnix's published page, Linux (man-pages and the GNU and util-linux manuals), FreeBSD, OpenBSD and NetBSD. Each row names its source. Where a manual is silent, this page is too. Compiled 2026-10-26. Found a mistake? Mail hackers@lists.solnix.io.