BSD 4_2 development
[unix-history] / usr / man / mano / netlogin.1
CommitLineData
11a514e8
C
1.TH NETLOGIN 1 "6 February 1980"
2.UC 4
3.ds s 1
4.ds o 1
5.SH NAME
6netlogin \- provide login name and password for a remote machine
7.SH SYNOPSIS
8.B netlogin
9.B \-m
10machine [
11.B \-l
12login
13]
14.SH DESCRIPTION
15The
16.I netlogin
17command sets the login name and password for the specified
18.I machine
19in a rather unusual way.
20The user should type (to the C shell)
21.IP
22setenv\ MACH\fImachine\fR\ \(ganetlogin\ \-m\ \fImachine\fR\(ga
23.LP
24or (to the default Version 7 ``Bourne'' shell)
25.IP
26MACH\fImachine\fR=\(ganetlogin\ \-m\ \fImachine\fR\(ga; export MACH\fImachine\fR
27.PP
28to his login shell. (Note the back-quotes).
29For example,
30.IP
31setenv\ MACHA\ `netlogin\ \-m\ A`
32.PP
33will prompt the user for his login name and password on the A machine and
34.IP
35setenv\ MACHA\ `netlogin\ \-m\ A \-l\ myname`
36.PP
37will prompt the user for the password to account `A:myname'.
38.PP
39The
40.IR net (\*s)
41command will read the environment looking for environment variables
42beginning with ``MACH'' and followed by a valid machine name on the
43local network.
44If found it will use that information rather than prompt the user
45every time he executes a network command.
46This environment information is ignored if login names and passwords
47are specified on the command line of network commands using the
48.B \-l
49and
50.B \-p
51options or in the
52.I \&.netrc
53file.
54.PP
55This procedure for specifying passwords is somewhat safer than
56putting the remote passwords in the
57.I \&.netrc
58file.
59The passwords in the environment are encrypted and the environment
60information is useless after the user logs out.
61Use the
62.IR printenv (\*o)
63command to see the encrypted password.
64.SH AUTHOR
65Eric Schmidt
66.SH "SEE ALSO"
67net(\*s), netrm(\*s), netq(\*s), netlog(\*s), netcp(\*s),
68netlpr(\*s), netmail(\*s), printenv(\*o), csh(\*o)
69.SH BUGS