|
|
1.1 root 1:
2:
3:
4: L.CMDS(5) 1986 L.CMDS(5)
5:
6:
7:
8: NNAAMMEE
9: L.cmds - UUCP remote command permissions file
10:
11: DDEESSCCRRIIPPTTIIOONN
12: The _L._c_m_d_s file contains a list of commands, one per line,
13: that are permitted for remote execution via _u_u_x(1C).
14:
15: The default search path is /bin:/usr/bin:/usr/ucb. To change
16: the path, include anywhere in the file a line of the form:
17:
18: PATH=/bin:/usr/bin:/usr/ucb
19:
20: Normally, an acknowledgment is mailed back to the requesting
21: site after the command completes. If a command name is suf-
22: fixed with ,,EErrrroorr, then an acknowledgment will be mailed
23: only if the command fails. If the command is suffixed with
24: ,,NNoo, then no acknowledgment will ever be sent. (These
25: correspond with the --zz and --nn options of _u_u_x, respectively.)
26:
27: For most sites, _L._c_m_d_s should only include the lines:
28:
29: rmail
30: ruusend
31:
32: News sites should add:
33:
34: PATH=/bin:/usr/bin:/usr/ucb:/usr/new
35: rnews,Error
36:
37: While file names supplied as arguments to _u_u_x commands will
38: be checked against the list of accessible directory trees in
39: _U_S_E_R_F_I_L_E(5), this check can be easily circumvented and
40: should not be depended upon. In other words, it is unwise
41: to include any commands in _L._c_m_d_s that accept local file
42: names. In particular, _s_h(1) and _c_s_h(1) are extreme risks.
43:
44: It is common (but hazardous) to include _u_u_c_p(1C) in _L._c_m_d_s;
45: see the NOTES section of _U_S_E_R_F_I_L_E.
46:
47: FFIILLEESS
48: /usr/lib/uucp/L.cmds
49: /usr/lib/uucp/UUAIDS/L.cmds L.cmds example.
50:
51: SSEEEE AALLSSOO
52: uucp(1C), uux(1C), USERFILE(5), uucico(8C), uuxqt(8C)
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63: Printed 7/4/90 April 1
64:
65:
66:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.