Return to L.cmds.5 CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / man / man5

Annotation of 43BSDTahoe/man/man5/L.cmds.5, revision 1.1.1.1

1.1       root        1: .\" Copyright (c) 1986 Regents of the University of California.
                      2: .\" All rights reserved.  The Berkeley software License Agreement
                      3: .\" specifies the terms and conditions for redistribution.
                      4: .\"
                      5: .\"    @(#)L.cmds.5    6.1 (Berkeley) 4/24/86
                      6: .\"
                      7: .TH L.CMDS 5 "April 24, 1986"
                      8: .UC 6
                      9: .SH NAME
                     10: L.cmds \- UUCP remote command permissions file
                     11: .SH DESCRIPTION
                     12: The
                     13: .I L.cmds
                     14: file contains a list of commands, one per line, that are permitted
                     15: for remote execution via
                     16: .IR uux (1C).
                     17: .PP
                     18: The default search path is /bin:/usr/bin:/usr/ucb. To change the path,
                     19: include anywhere in the file a line of the form:
                     20: .PP
                     21: .nf
                     22:        PATH=/bin:/usr/bin:/usr/ucb
                     23: .fi
                     24: .PP
                     25: Normally, an acknowledgment is mailed back to the requesting
                     26: site after the command completes. If a command name is suffixed with
                     27: .BR ,Error ,
                     28: then an acknowledgment will be mailed only if the command fails.
                     29: If the command is suffixed with
                     30: .BR ,No ,
                     31: then no acknowledgment will ever be sent. (These correspond with
                     32: the
                     33: .B \-z
                     34: and
                     35: .B \-n
                     36: options of
                     37: .IR uux ,
                     38: respectively.)
                     39: .PP
                     40: For most sites,
                     41: .I L.cmds
                     42: should only include the lines:
                     43: .PP
                     44: .nf
                     45:        rmail
                     46:        ruusend
                     47: .fi
                     48: .PP
                     49: News sites should add:
                     50: .PP
                     51: .nf
                     52:        PATH=/bin:/usr/bin:/usr/ucb:/usr/new
                     53:        rnews,Error
                     54: .fi
                     55: .PP
                     56: While file names supplied as arguments to
                     57: .I uux
                     58: commands will be checked against the list of accessible directory trees in
                     59: .IR USERFILE (5),
                     60: this check can be easily circumvented and should not be depended upon.
                     61: In other words, it is unwise to include any commands in
                     62: .I L.cmds
                     63: that accept local file names. In particular,
                     64: .IR sh (1)
                     65: and
                     66: .IR csh (1)
                     67: are extreme risks.
                     68: .PP
                     69: It is common (but hazardous) to include
                     70: .IR uucp (1C)
                     71: in
                     72: .IR L.cmds ;
                     73: see the NOTES section of
                     74: .IR USERFILE .
                     75: .SH FILES
                     76: .ta \w'/usr/lib/uucp/UUAIDS/L.cmds   'u
                     77: .nf
                     78: /usr/lib/uucp/L.cmds
                     79: /usr/lib/uucp/UUAIDS/L.cmds    L.cmds example.
                     80: .fi
                     81: .SH SEE ALSO
                     82: uucp(1C), uux(1C), USERFILE(5), uucico(8C), uuxqt(8C)

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.