PUMP

NAME
SYNOPSIS
DESCRIPTION
COMMAND-LINE OPTIONS
LOGGING
CONFIG FILE
BUGS
QUIBBLE

NAME

pump − configure network interface via BOOTP or DHCP protocol

SYNOPSIS

/sbin/pump [-krRsd?] [-c ARG] [-h hostname] [-i iface] [-l hours] [--lookup-hostname] [--usage]

DESCRIPTION

pump is a daemon that manages network interfaces that are controlled by either the DHCP or BOOTP protocol.

While pump may be started manually, it is normally started automatically by the /sbin/ifup script for devices configured via BOOTP or DHCP.

Once pump is managing an interface, you can run pump to query the status of that interface. For example,
/sbin/pump -i eth0 --status

will print the current status of device eth0.

COMMAND-LINE OPTIONS

LOGGING

Pump logs a good deal of information to syslog, much of it at the DEBUG level. If you’re having trouble, it’s a good idea to turn up syslog’s logging level.

CONFIG FILE

Pump supports a simple configuration file which lets you tune its behavior. By default, it looks at /etc/pump.conf, though the -c option lets you override that.

The configuration file is line oriented, and most line contains a directive followed by zero or more arguments. Arguments are handled similar to how shells handle command arguments, allowing the use of quotes and backslash escapes. Comments are allowed, and must begin with a # character, and spaces and tabs are ignored.

Directives may be specified at two levels, global and specific. Global directives change pump’s behavior for all of the devices which it manages, while specific directives change pump’s behavior for a single device. Later directives always override earlier ones.

Here is an example /etc/pump.conf:

# sample /etc/pump.conf file

domainsearch "my.own.org own.org at.work.com"
retries 3

device eth1 {
    nodns
}

This configuration file tells pump to use a specific DNS search path rather deriving one from the DHCP or BOOTP server response, to retry each request 3 times (for a total of 4 tries), and not to change any DNS configuration when it’s configuring the eth1 device.

Here is a complete list of directives:

device device

Specify specific directives for the indicated device. This directive must be followed by a {, and the list of specific directives must end with a } on its own line. These directives may not be nested.

domainsearch searchpath

Rather then deriving the DNS search path (for /etc/resolv.conf), use the one which is given. As a machine only has a single DNS search path, this directive may only be used globally.

nodns

Don’t create a new /etc/resolv.conf when this interface is configured. This directive may only be used within a device directive.

retries count

Retry each phase of the DHCP process count times.

timeout count

Don’t let any one step of the DHCP process take more then count seconds.

script executable-filename

When events occur in negotiation with the server, calls the given executable or script. Scripts are called when a lease is granted, when a renewal is negotiated, and when the interface is brought down and the address released. The scripts are called with two or three arguments, depending on the condition, as documented in the table above.

BUGS

Probably limited to Ethernet, might work on PLIP, probably not ARCnet and Token Ring. The configuration file should let you do more things.

Submit bug reports at the Bug Track link at http://developer.redhat.com/

QUIBBLE

A pump, like a boot[p], is something you wear on your foot. Some of us like the name (I know, hard to believe)!