blob: ae4955a2a6cb4ca84ae17d43d9c3709cfb0aeb59 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-h (September 30, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>Network logins</TITLE>
<META NAME="description" CONTENT="Network logins">
<META NAME="keywords" CONTENT="sag">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<LINK REL=STYLESHEET HREF="sag.css">
</HEAD>
<BODY LANG="EN" >
<A NAME="tex2html481" HREF="node16.html"><IMG WIDTH=37 HEIGHT=24 ALIGN=BOTTOM ALT="next" SRC="./next_motif.gif"></A> <A NAME="tex2html479" HREF="node8.html"><IMG WIDTH=26 HEIGHT=24 ALIGN=BOTTOM ALT="up" SRC="./up_motif.gif"></A> <A NAME="tex2html473" HREF="node14.html"><IMG WIDTH=63 HEIGHT=24 ALIGN=BOTTOM ALT="previous" SRC="./previous_motif.gif"></A> <A NAME="tex2html483" HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="./contents_motif.gif"></A> <A NAME="tex2html484" HREF="node114.html"><IMG WIDTH=43 HEIGHT=24 ALIGN=BOTTOM ALT="index" SRC="./index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME="tex2html482" HREF="node16.html">Network file systems</A>
<B>Up:</B> <A NAME="tex2html480" HREF="node8.html">Major services in a </A>
<B> Previous:</B> <A NAME="tex2html474" HREF="node14.html">Networking</A>
<BR> <P>
<H2><A NAME="SECTION00337000000000000000">Network logins</A></H2>
<P>
Network logins work a little differently than normal logins.
There is a separate physical serial line for each terminal via
which it is possible to log in. For each person logging in via
the network, there is a separate virtual network connection,
and there can be any number of these<A NAME="tex2html7" HREF="footnode.html#231"><IMG ALIGN=BOTTOM ALT="gif" SRC="./foot_motif.gif"></A>. It is
therefore not possible to run a separate <tt>getty</tt><A NAME="369"> </A> for each
possible virtual connection. There are also several different
ways to log in via a network, <tt>telnet</tt><A NAME="371"> </A> and <tt>rlogin</tt><A NAME="373"> </A> being
the major ones in TCP/IP networks.
<P>
Network logins have, instead of a herd of <tt>getty</tt><A NAME="375"> </A>s, a
single daemon per way of logging in (<tt>telnet</tt><A NAME="377"> </A> and <tt>rlogin</tt><A NAME="379"> </A>
have separate daemons) that listens for all incoming login attempts.
When it notices one, it starts a new instance of itself to handle that
single attempt; the original instance continues to listen for
other attempts. The new instance works similarly to <tt>getty</tt><A NAME="381"> </A>.
<A NAME="290"> </A>
<A NAME="291"> </A>
<P>
<BR> <HR>
<P><ADDRESS>
<I>Lars Wirzenius <BR>
Sat Nov 15 02:32:11 EET 1997</I>
</ADDRESS>
</BODY>
</HTML>
|
