This new implementation of the UDS service is built on top of the libsockevent library. It thereby inherits all the advantages that libsockevent brings. However, the fundamental restructuring required for that change also paved the way for resolution of a number of other important open issues with the old UDS code. Most importantly, the rewrite brings the behavior of the service much closer to POSIX compliance and NetBSD compatibility. These are the most important changes: - due to the use of libsockevent, UDS now supports multiple suspending calls per socket and a large number of standard socket flags and options; - socket address matching is now based on <device,inode> lookups instead of canonized path names, and socket addresses are no longer altered either due to canonization or at connect time; - the socket state machine is now well defined, most importantly resolving the erroneous reset-on-EOF semantics of the old UDS, but also allowing socket reuse; - sockets are now connected before being accepted instead of being held in connecting state, unless the LOCAL_CONNWAIT option is set on either the connecting or the listening socket; - connect(2) on datagram sockets is now supported (needed by syslog), and proper datagram socket disconnect notification is provided; - the receive queue now supports segmentation, associating ancillary data (in-flight file descriptors and credentials) with each segment instead of being kept fully separately; this is a POSIX requirement (and needed by tmux); - as part of the segmentation support, the receive queue can now hold as many packets as can fit, instead of one; - in addition to the flags supported by libsockevent, the MSG_PEEK, MSG_WAITALL, MSG_CMSG_CLOEXEC, MSG_TRUNC, and MSG_CTRUNC send and receive flags are now supported; - the SO_PASSCRED and SO_PEERCRED socket options are replaced by LOCAL_CREDS and LOCAL_PEEREID respectively, now following NetBSD semantics and allowing use of NetBSD libc's getpeereid(3); - memory usage is reduced by about 250 KB due to centralized in-flight file descriptor tracking, with a limit of OPEN_MAX total rather than of OPEN_MAX per socket; - memory usage is reduced by another ~50 KB due to removal of state redundancy, despite the fact that socket path names may now be up to 253 bytes rather than the previous 104 bytes; - compared to the old UDS, there is now very little direct indexing on the static array of sockets, thus allowing dynamic allocation of sockets more easily in the future; - the UDS service now has RMIB support for the net.local sysctl tree, implementing preliminary support for NetBSD netstat(1). Change-Id: I4a9b6fe4aaeef0edf2547eee894e6c14403fcb32 |
||
|---|---|---|
| .. | ||
| lists | ||
| attrs | ||
| checkflist | ||
| comments | ||
| culldeps | ||
| deps | ||
| descrs | ||
| getdirs.awk | ||
| join.awk | ||
| listpkgs | ||
| Makefile | ||
| makeflist | ||
| makeobsolete | ||
| makeplist | ||
| makesrctars | ||
| makesums | ||
| maketars | ||
| metalog.subr | ||
| mkvars.mk | ||
| README | ||
| regpkg | ||
| regpkgset | ||
| sets.subr | ||
| sort-list | ||
| syspkgdeps | ||
| TODO | ||
| versions | ||
# $NetBSD: README,v 1.13 2013/08/06 22:33:59 soren Exp $
the scripts should be run from the directory where they reside.
makeflist: output the list of files that should be in a
distribution, according to the contents of the
'lists' directory.
checkflist: check the file list (as internally generated
by makeflist) against the tree living in $DESTDIR.
(that tree should be made with 'make distribution'.)
maketars: make tarballs of the various sets in the distribution,
based on the contents of the lists, the tree in
$DESTDIR, and put the tarballs in $RELEASEDIR.
Note that this script _doesn't_ create the 'secr'
distribution, because (for now) it requires
manual intervention to get the binaries right...
(i'll add another script to create that dist, later.)
what's in 'lists':
lists describing file sets. There are two sets of lists per file
set: machine dependent and machine-independent files. (there's
also another file in the 'man' dir, which is used by the 'man'
and 'misc' sets, but that's explained later.)
There is one machine-independent file, named "mi". There are
N machine-dependent files (one per architecture), named "md.${ARCH}".
the sets are as follows:
base: the base binary set. excludes everything described
below.
comp: compiler tools. All of the tools relating to C, C++,
and FORTRAN (yes, there are two!) that are in the
tree. This includes includes, the linker, tool chain,
and the .a versions of the libraries. (obviously,
base includes ldd, ld.so, and the shared versions.
base also includes 'cpp', because that's used by X11.)
includes the man pages for all the binaries contained
within. Also, includes all library and system call
manual pages.
debug: Debugging libraries (_g.a/MKDEBUGLIB) and (.debug/MKDEBUG)
binaries.
etc: /etc, and associated files (/var/cron/tabs, /root,
etc.). things that shouldn't be blindly reinstalled
on an upgrade.
games: the games and their man pages.
man: all of the man pages for the system, except those
listed elsewhere (e.g. in comp, games, misc, text).
Includes machine-dependent man pages for this CPU.
misc: share/dict, share/doc, and the machine-dependent
man pages for other CPUs which happen to always
be installed.
modules: stand/${MACHINE}/${OSRELEASE}/modules kernel modules
tests: unit, regression, integration and stress tests for the
whole system.
text: text processing tools. groff and all of its friends.
includes man pages for all bins contained within.
Each set must contain "./etc/mtree/set.<set name>" within the mi
list. Failure to add this will break unprivileged builds.