1autopush(1M) System Administration Commands autopush(1M)
2
3
4
6 autopush - configures lists of automatically pushed STREAMS modules
7
9 autopush -f filename
10
11
12 autopush -g -M major -m minor
13
14
15 autopush -r -M major -m minor
16
17
19 The autopush command configures the list of modules to be automatically
20 pushed onto the stream when a device is opened. It can also be used to
21 remove a previous setting or get information on a setting.
22
24 The following options are supported:
25
26 -f filename
27
28 Sets up the autopush configuration for each driver according to the
29 information stored in filename. An autopush file consists of lines
30 of four or more fields, separated by spaces as shown below:
31
32 major minor last-minor module1 module2 ... module8
33
34
35 The first field is a string that specifies the major device name,
36 as listed in the /kernel/drv directory. The next two fields are
37 integers that specify the minor device number and last-minor device
38 number. The fields following represent the names of modules. If
39 minor is −1, then all minor devices of a major driver specified by
40 major are configured, and the value for last-minor is ignored. If
41 last-minor is 0, then only a single minor device is configured. To
42 configure a range of minor devices for a particular major, minor
43 must be less than last-minor.
44
45 The remaining fields list the names of modules to be automatically
46 pushed onto the stream when opened, along with the position of an
47 optional anchor. The maximum number of modules that can be pushed
48 is eight. The modules are pushed in the order they are specified.
49 The optional special character sequence [anchor] indicates that a
50 STREAMS anchor should be placed on the stream at the module previ‐
51 ously specified in the list; it is an error to specify more than
52 one anchor or to have an anchor first in the list.
53
54 A nonzero exit status indicates that one or more of the lines in
55 the specified file failed to complete successfully.
56
57
58 -g
59
60 Gets the current configuration setting of a particular major and
61 minor device number specified with the -M and -m options respec‐
62 tively and displays the autopush modules associated with it. It
63 will also return the starting minor device number if the request
64 corresponds to a setting of a range (as described with the -f
65 option).
66
67
68 -m minor
69
70 Specifies the minor device number.
71
72
73 -M major
74
75 Specifies the major device number.
76
77
78 -r
79
80 Removes the previous configuration setting of the particular major
81 and minor device number specified with the -M and -m options
82 respectively. If the values of major and minor correspond to a pre‐
83 viously established setting of a range of minor devices, where
84 minor matches the first minor device number in the range, the con‐
85 figuration would be removed for the entire range.
86
87
89 The following exit values are returned:
90
91 0
92
93 Successful completion.
94
95
96 non-zero
97
98 An error occurred.
99
100
102 Example 1 Using the autopush command.
103
104
105 The following example gets the current configuration settings for the
106 major and minor device numbers as indicated and displays the autopush
107 modules associated with them for the character-special device
108 /dev/term/a:
109
110
111 example# autopush -g -M 29 -m 0
112 Major Minor Lastminor Modules
113 29 0 1 ldterm ttcompat
114
115
116
118 /etc/iu.ap
119
121 See attributes(5) for descriptions of the following attributes:
122
123
124
125
126 ┌─────────────────────────────┬─────────────────────────────┐
127 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
128 ├─────────────────────────────┼─────────────────────────────┤
129 │Availability │SUNWcsu │
130 └─────────────────────────────┴─────────────────────────────┘
131
133 dladm(1M), ttymon(1M), attributes(5), ldterm(7M), sad(7D),
134 streamio(7I), ttcompat(7M)
135
136
137
138
140 The use of the autopush command is obsolete for networking data-links.
141 The preferred method of configuring a list of automatically pushed
142 STREAMS modules on a given networking data-link interface is the
143 dladm(1M) autopush link property.
144
145
146 Because network devices are self-cloning, the autopush command is inad‐
147 equate for networking devices. The granularity of the autopush com‐
148 mand's configuration is driver-wide, and not per-interface as one might
149 expect. Another reason not to use autopush is that administrators are
150 more familiar with the names of their network interfaces than with
151 device major and minor numbers. The dladm(1M) command allows the con‐
152 figuration using data-link interface names.
153
154
155
156SunOS 5.11 15 Feb 2008 autopush(1M)