fix "under development line"
[unix-history] / usr / src / sbin / startslip / startslip.1
.\" Copyright (c) 1990, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
.\"
.\" %sccs.include.redist.roff%
.\"
.\" @(#)startslip.1 8.1 (Berkeley) %G%
.\"
.Dd
.Dt STARTSLIP 1
.Os BSD 4.4
.Sh NAME
.Nm startslip
.Nd dial up and login to a slip server
.Sh SYNOPSIS
.Nm startslip
.Op Fl d
.Op Fl s Ar string
.Op Fl A Ar annexname
.Op Fl F Ar flowcontrol
.Ar device user passwd
.Sh DESCRIPTION
.Nm Startslip
opens the specified
.Ar device .
.Pp
Once carrier is asserted
.Nm startslip
attempts to login as the specified
.Ar user
with the given
.Ar password .
If successful, it puts the device into the slip line discipline.
If carrier drops and a
.Dv SIGHUP
is sent to
.Nm startslip ,
it closes the device and attempts to repeat the dialup and login sequence.
.Pp
Available options:
.Bl -tag -width Ar
.It Fl d
.Nm Startslip
prints out debugging information about what it is trying to do.
.It Fl s Ar string
The optional
.Ar string
is written to
.Ar device .
For a dialup modem,
the string is used to specify a dial sequence.
.It Fl A Ar annexname
.Nm Startslip
assumes it is connecting to a Xylogics Annex box and engages in an
appropriate dialog using the
.Ar user
and
.Ar passwd
arguments.
The
.Ar annexname
argument is a string that is used to match against the Annex prompt
to determine when a connection has been established.
.It Fl F Ar flowcontrol
Determines the type of flow control used on
.Ar device .
Choices for
.Ar flowcontrol
are
``none'' for no flow control (the default),
``hw'' for hardware RTS/CTS flow control and
``sw'' for software XON/XOFF flow control.
.El
.Sh SEE ALSO
.Xr sliplogin 8
.Sh HISTORY
The
.Nm startslip
appeared in
.Bx 4.4 .