Programs:
-* md5sum (Colin Plumb's or the GNU version)
-* GNU m4
+* md5sum (GNU textutils; alternatively, Colin Plumb's, as shipped with
+ Debian in the `dpkg' package) - used during build only
* GNU make
-* GNU flex
* GCC is preferred but other compilers ought to work (though
no portability testing has yet been done). ANSI C only.
ints must be at least 32 bits.
-* A sensible /bin/cat which notices write errors (ie not
- SunOS4, BSD 4.3, or many others.)
+* A sensible `cat' which notices write errors (ie not SunOS4, BSD 4.3,
+ or many others. GNU textutils has one. NB that this `cat' is used
+ at runtime and must be first on the system default PATH, so probably
+ in /bin.)
+* GNU m4 } if you don't want to change those bits of source
+* GNU flex } you can do without these
C Library:
open(O_WRONLY), close(), dup2, EPIPE, SIGPIPE, &c.
(ie, opening pipes with O_RDWR never blocks; EPIPE happens
if you write with no readers; EOF happens if you read with
- no buffered data and writers)
+ no buffered data and writers);
* POSIX signal handling - sigaction(2), sigprocmask(2), sigsuspend(2);
+* POSIX sessions - setsid(2) (for -daemon flag).
To format the documentation:
* initgroups(3) must use setgroups(2) and dynamic
linking must allow overriding setgroups(2) for initgroups(3);
+EXIT STATUS CODES
+
+For information about uservd's exit status, see uservd(8).
+
+The daemon's per-request children will note the success level of its
+request in its exit status. This will not usually be logged unless it
+is higher than those listed below; they are presented here for
+completeness and as programming documentation.
+
+ 2 - The connection was just an internal version check.
+
+ 4 - The client requested that the service be disconnected. This
+ includes normal termination, which is achieved by having the
+ server tell the client that the service has completed and waiting
+ for the client to tell it to disconnect.
+
+ 8 - The client closed its end of the socket when this would not
+ usually have been expected, causing an EPIPE or unexpected EOF in
+ the server. This is not an error condition - it can happen, for
+ example, if the client receives a fatal signal of some kind from
+ its execution environment (eg its controlling terminal).
+
+ 10 - The per-request child wishes the server to check whether it is
+ still the uservd.
+
+ 12 - The service failed onm the service side in an expected and
+ controlled manner, for example because it was rejected in the
+ configuration files.
+
+ 16 - A fatal system call failure or other general error occurred,
+ which ought not to have happened at all, barring system resource
+ shortages.
+
+ 20 - The client sent invalid data to the server, after the client
+ dropped all its system privilege. On some systems this can be
+ caused by a malicious calling user.
+
+ SIGABRT/SIGIOT - The client sent invalid data to the server before it
+ dropped all its system privileges, or some other unexpected
+ internal error occurred. This can also occur if an attempt to
+ block signals using sigprocmask fails.
+
+ 0-3,5-7,9,11,13-15,17-19 are not currently used by normal children.
+
REENTRANCY IN THE LIBC:
We assume, both in the client and server, that it is safe to use one
The bug is actually in your system header files, for not specifying
the number and types of arguments to signal handler functions when
they cast in the SIG_IGN and SIG_DFL macros.
+
+DEBUGGING VERSION
+
+If you run configure with --enable-debug, a debugging version will be
+built. This will look in the current directory (the build directory)
+for the base of various things, including the IPC area (which you must
+therefore construct yourself). The debugging version will produce
+extra output at various points. It will not attempt to call
+setgroups(), instead just checking that the groups list is right, so
+it will work non-setuid if the daemon is invoked as the service user.
+The daemon won't fork for each request; instead, it will handle a
+single request and exit.
+
+There may be other changes. Consult the code for details. Making the
+debugging version of the client or daemon setuid root is probably a
+bad idea. They may not work if they are run as different users.
+
+
+COPYRIGHT
+
+This file, INSTALL, contains installation instructions and other
+details for userv.
+
+userv is
+Copyright (C)1996-2000 Ian Jackson <ian@davenant.greenend.org.uk>.
+Copyright (C)2000 Ben Harris <bjh21@cam.ac.uk>
+
+userv is free software; you can redistribute it and/or modify it under
+the terms of the GNU General Public License as published by the Free
+Software Foundation; either version 2 of the License, or (at your
+option) any later version.
+
+This program is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with userv as the file COPYING; if not, email me at the address
+above or write to the Free Software Foundation, 59 Temple Place -
+Suite 330, Boston, MA 02111-1307, USA.
~ian / userv.git / blobdiff