DebianNet(3pm) Linux Programmer's Manual DebianNet(3pm)NAME
DebianNet.pm - create, remove, enable or disable entry in /etc/inetd.conf
SYNOPSIS
require DebianNet;
DebianNet::add_service($newentry, $group);
DebianNet::remove_service($entry);
DebianNet::enable_service($service, $pattern);
DebianNet::disable_service($service, $pattern);
DESCRIPTION
You can use the functions in DebianNet.pm to to add, remove, enable or disable entries in the /etc/inetd.conf file. After the
/etc/inetd.conf file has been changed, a SIGHUP signal will be sent to the inetd process to make sure that inetd will use the new
/etc/inetd.conf file. The functions can also be used to add entries that are commented out by default. They will be treated like normal
entries. That also means that if you already have an entry that is commented out you can't add an entry for the same service without remov-
ing the old one first.
The DebianNet functions treat entries that are commented out by a single '#' character as entries that have been commented out by a user.
It won't change such entries.
For shell scripts you can also use the update-inetd command. See update-inetd(8) for further information.
VARIABLES
$DebianNet::inetdcf = "FILENAME";
Use FILENAME instead of /etc/inetd.conf (e.g. for testing purposes).
$DebianNet::sep = "#<off># ";
"#<off># " will be used as the default comment characters. You can use this option to specify different comment characters. This
is only necessary if you have to deal with two (or more) services of the same name.
$DebianNet::multi = "true";
If you want to disable/remove more than one entry at a time you should use this option. If you try to remove more than one entry at
a time without using this option the program will show a warning and asks the user if he want to continue.
$DebianNet::verbose = "true";
Explain what is being done.
FUNCTIONS
DebianNet::add_service($newentry, $group);
Add $newentry to the group $group of the /etc/inetd.conf file. If the entry already exist it will be enabled (it will also detect
entries with different program options). Using $group is optional (the default group is the group OTHER). If the group does not
exist the entry will be placed at the end of the file.
DebianNet::remove_service($entry);
Remove $entry from /etc/inetd.conf . You can use a regular expression to remove the entry.
DebianNet::enable_service($service, $pattern);
Enable $service (e.g. "ftp") in /etc/inetd.conf . Using $pattern is optional. It can be used to select a service. You only need
this option if you have two (or more) services of the same name. An example: you have three ftp entries in the /etc/inetd.conf file
(all disabled by default) and you want to enable the entry which uses the wu-ftpd daemon. To do this, use the pattern "wu-ftpd" (or
any other regular expression that matches this entry).
DebianNet::disable_service($service, $pattern);
Disable SERVICE (e.g. "ftp") in /etc/inetd.conf . Using $pattern is optional (see above).
AUTHORS
Peter Tobias, <tobias@et-inf.fho-emden.de>
Ian Jackson <iwj10@cus.cam.ac.uk>
Linux 21 September 1995 DebianNet(3pm)
Check Out this Related Man Page
inetd.conf(4) Kernel Interfaces Manual inetd.conf(4)NAME
inetd.conf - configuration file for inetd
DESCRIPTION
On invocation, the daemon reads its configuration information from the configuration file, and possibly at some later time in response to a
signal (see inetd(1M)).
Each line in the file is treated either as a comment or as configuration information for a given service Comments are denoted by a at the
beginning of a line. Noncomment lines contain seven or nine required fields, depending on the service name specified in the first field.
Fields are separated by tabs and/or spaces. A line can be continued if it terminates with a Each configuration line in the file contains
the following fields in the order indicated:
o service name
o socket type
o protocol
o
o user
o server program
o program number (NFS RPC services only)
o version number (NFS RPC services only)
o server program arguments
Fields are constructed as follows:
service name if the server is RPC-based (NFS); otherwise, the name of a valid service in file For example, for the service
(see remsh(1)), for the service (see rlogin(1)), and for the service (see telnet(1)).
socket type or depending on whether the server socket is a stream or a datagram socket, or intended for a program built
using the XTI API.
protocol Must be a valid protocol as given in for example, or For an XTI service, the protocol field is treated as:
o A network_ID for an RPC service, (see netconfig(4)).
o A device name in the directory for a non-RPC service. For example, if is specified, the path will be used.
For IPv6 applications the protocol is specified as either or
Specifies whether should act as a single- or multi-threaded server.
Instructs to start one server to handle an incoming request, and cease listening for new requests for the same
service until the server that started has exited.
Same as but instructs to expect the server to accept the incoming request.
Instructs to start one server for each incoming request.
Most UDP-based services use for this field, while TCP-based services use
user User ID to be used when the server is running.
server program Absolute path name of the program executed by when it finds a request on the server's socket.
server program arguments
Arguments to the server program. The same as in normal use, starting with which is the name of the program.
If service name is (NFS RPC services), two extra fields are required. They must appear between the server program field and the server
program arguments field:
program number Defines a particular service grouping and is unique.
version number Version supported by the RPC service. This number can be a single value, or a range, if the program handles
multiple versions; for example, or Ranges are separated by a hyphen Version numbers allow RPC protocols to be
extended and modified, and make it possible for old and new protocols to share the same server process.
Built-in inetd Services
The daemon provides several "trivial" services internally by use of built-in routines (see inetd(1M) for a list of these services). To
configure an internal service, specify as the server program name, and omit the server program arguments field.
EXAMPLES
Configure the service to use TCP protocol, and run the server as user
The above is an example of the remsh utility run in the IPv4 mode. To run the above utility in the IPv6 mode, the protocol must be changed
to Thus the above configuration is re-written as below to run in mode.
Configure the FTP server to timeout an inactive session after 75 seconds.
The above ftp service can be run in IPv6 mode using the configuration shown below:
Configure an RPC-based service. Note that the service name field contains and two more fields are used: the program number(100008) and
version number(1).
Configure to use the built-in TCP service.
AUTHOR
was developed by the University of California, Berkeley.
NFS was developed by Sun Microsystems, Inc.
SEE ALSO inetd(1M), exec(2), fork(2), inetd.sec(4), protocols(4), services(4).
inetd.conf(4)