Installation guide

• SocketType , which is either a stream value or a datagram value.
•
ProtocolName , which is one of the protocols in the /etc/protocols
file.
•
Wait/NoWait , which determines whether the inetd daemon waits for
a datagram server to release the socket. (Stream sockets are always
NoWait.)
•
UserName , which specifies the user name that the inetd daemon
should use to start the server.
•
ServerPath , which specifies the full pathname of the server the inetd
daemon should execute.
•
ServerArguments , which are the command-line arguments passed to
the server.
The new
UserName field allows you to specify what user name inetd
should assign to a server when it starts. On ULTRIX systems, servers were
automatically started with the root user name. For compatibility, specify
root in this field for each service. However, if your server does not need root
privileges, consider specifying another user name in this field. As long as
your server does not need root privileges, you should not notice a difference
between the operation of an ULTRIX server and the operation of a
DIGITAL UNIX server that is started under a user name other than root.
5.8 Configuring the mountd Daemon for ULTRIX
Compatibility
The mountd daemon works with other daemons to provide the NFS service.
This daemon checks the access permission of the client and returns a
pointer to the file system or directory that is to be mounted by the NFS
service.
By default, the mountd daemon on DIGITAL UNIX systems accepts
requests only from the superuser of a remote system. By contrast, the
ULTRIX daemon accepts mount requests from any user.
You can configure the mountd daemon on a DIGITAL UNIX system to
accept requests from users other than the superuser. To do so, start the
daemon with the -n option, as shown:
# /usr/sbin/mountd -n
This command starts the daemon so that it operates the same as the
ULTRIX mountd daemon.
Migrating Your ULTRIX System and Network Environment 5–11