Penguin
Recent Changes
Annotated edit history of pump(8) version 1 showing authors affecting page license. View with all changes included.
Rev Author # Line
1 perry 1 PUMP
2 !!!PUMP
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 COMMAND-LINE OPTIONS
7 LOGGING
8 CONFIG FILE
9 BUGS
10 QUIBBLE
11 ----
12 !!NAME
13
14
15 pump - configure network interface via BOOTP or DHCP protocol
16 !!SYNOPSIS
17
18
19 /sbin/pump [[-krRsd?] [[-c ''ARG''] [[-h ''hostname'']
20 [[-i ''iface''] [[-l ''hours''] [[--lookup-hostname]
21 [[--usage]
22 !!DESCRIPTION
23
24
25 pump is a daemon that manages network interfaces that are
26 controlled by either the DHCP or BOOTP
27 protocol.
28
29
30 While pump may be started manually, it is normally started
31 automatically by the /sbin/ifup script for devices
32 configured via BOOTP or DHCP.
33
34
35 Once pump is managing an interface, you can run pump to
36 query the status of that interface. For example,
37 /sbin/pump -i eth0 --status
38 will print the current status of device eth0.
39 !!COMMAND-LINE OPTIONS
40 !!LOGGING
41
42
43 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.
44 !!CONFIG FILE
45
46
47 Pump supports a simple configuration file which lets you
48 tune its behavior. By default, it looks at
49 ''/etc/pump.conf'', though the __-c__ option lets you
50 override that.
51
52
53 The configuration file is line oriented, and most line
54 contains a directive followed by zero or more arguments.
55 Arguments are handled similar to how shells handle command
56 arguments, allowing the use of quotes and backslash escapes.
57 Comments are allowed, and must begin with a # character, and
58 spaces and tabs are ignored.
59
60
61 Directives may be specified at two levels, global and
62 specific. Global directives change pump's behavior for all
63 of the devices which it manages, while specific directives
64 change pump's behavior for a single device. Later directives
65 always override earlier ones.
66
67
68 Here is an example /etc/pump.conf:
69
70
71 # sample /etc/pump.conf file
72 domainsearch
73 This configuration file tells pump to use a specific DNS search path rather than 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.
74
75
76 Here is a complete list of directives:
77
78
79 __device__ ''device''
80
81
82 Specify specific directives for the indicated device. This
83 directive must be followed by a {, and the list of specific
84 directives must end with a } on its own line. These
85 directives may not be nested.
86
87
88 __domainsearch__ ''searchpath''
89
90
91 Rather then deriving the DNS search path (for
92 /etc/resolv.conf), use the one which is given. As a machine
93 only has a single DNS search path, this directive may only
94 be used globally.
95
96
97 __nonisdomain__
98
99
100 Don't set a new NIS domain. Normally __pump__ sets the
101 system's NIS domain if an NIS domain is specified by the
102 dhcp server and the current NIS domain is empty or
103 __localdomain__. This directive may only be used within a
104 __device__ directive.
105
106
107 __nodns__
108
109
110 Don't create a new /etc/resolv.conf when this interface is
111 configured. This directive may only be used within a
112 __device__ directive.
113
114
115 __nogateway__
116
117
118 Ignore any default gateway suggested by the DHCP server for
119 this device. This can be usefull on machines with multiple
120 ethernet cards.
121
122
123 __retries__ ''count''
124
125
126 Retry each phase of the DHCP process ''count''
127 times.
128
129
130 __timeout__ ''count''
131
132
133 Don't let any one step of the DHCP process take more then
134 ''count'' seconds.
135
136
137 __script__ ''executable-filename''
138
139
140 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.
141 !!BUGS
142
143
144 Probably limited to Ethernet, might work on PLIP, probably
145 not ARCnet and Token Ring. The configuration file should let
146 you do more things.
147
148
149 Submit bug reports at the Bug Track link at
150 http://developer.redhat.com/
151 !!QUIBBLE
152
153
154 A pump, like a boot[[p], is something you wear on your foot.
155 Some of us like the name (I know, hard to
156 believe)!
157 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.