L.sys man page on Ultrix

Man page or keyword search:  
man Server   3690 pages
apropos Keyword Search (all sections)
Output format
Ultrix logo
[printable version]

L.sys(5)							      L.sys(5)

Name
       L.sys - information needed to connect to a system

Syntax
       /usr/lib/uucp/L.sys

Description
       The  utility  uses the file.  The file contains entries for each remote
       system that the local system can call and for each  remote  system  for
       which  the local system accepts calls but does not call.	 More than one
       line can be used for a particular remote system.	  In  this  case,  the
       additional  lines  represent  alternative  communication paths that are
       tried in sequential order.

       The format of each entry, with each field separated by blanks or	 tabs,
       is:

       system-name time device class phone login

       system-name
	      The name of the remote system.

       time   A	 string	 that  indicates the days of the week and the times of
	      day   when   the	 system	  can	be   called   (for    example,
	      MoTuTh0800-1740).

	      The day portion may be a list containing:

	      Su Mo Tu We Th Fr Sa

	      The day may also be Wk for any weekday or Any for any day.

	      You  can indicate hours in a range (for example, 0800-1230).  If
	      you do not specify a time, calls will be allowed at any time.

	      Note that a time range that spans 0000 is permitted.  For	 exam‐
	      ple,  0800-0600  means  that  all times are allowed except times
	      between 6 AM and 8 AM.

	      Multiple date specifications that are separated  by  a  vertical
	      bar (|) are allowed.  For example, Any0100-0600|Sa|Su means that
	      the system can be called any day between 1 AM and y  AM  or  any
	      time on Saturday and Sunday.

	      An  optional subfield is available to indicate the minimum time,
	      in minutes, before retrying a failed connection.	A failed  con‐
	      nection attempt is a login failure, as opposed to a dialing con‐
	      nection failure.	The subfield separator is a  comma  (,).   For
	      example, Any, 9 means call any time, but wait at least 9 minutes
	      after a failure has occurred.

       device Either the ACU or the hard-wired device used for the call.   For
	      the  hard-wired  device,	use  the last part of the special file
	      name (for example, tty2).

       class  The line speed for the call (for example, 1200).	The  exception
	      is  when	the  BC library routine dialout is available, in which
	      case this is the dialout class.

       phone  The telephone number, made up of an optional alphabetic abbrevi‐
	      ation  and  a numeric part.  The abbreviation should be one that
	      appears in the file (for example, ct5900, nh6511).  If a numeric
	      number  is used, it should be given in full.  For the hard-wired
	      devices, this field contains the same string  as	used  for  the
	      device field.

       login  The login information, given as a series of fields and subfields
	      in this format:
	      expect1[-]-expect2] send ...

	      The expect1 argument is the string the local system  expects  to
	      read when logging in to the remote system, and the send argument
	      is the string the local system is to send when the expect string
	      is  received.   If two double quotation marks ("") are specified
	      instead of the expect1 argument, nothing is  expected  from  the
	      remote system.

	      The  sendspecial	argument  specifies  a special character to be
	      sent to the  remote  system  if  the  expect1  argument  is  not
	      received.	 If sendspecial is omitted, and two dashes (--) follow
	      the expect1 argument, the local system sends a  carriage	return
	      to the remote system.

	      Other special characters are:

	      EOT	Send an EOT character

	      BREAK#	Send # break sequences (default is 3)

	      PAUSE#	Pause # seconds (default is 5)

	      \d	Pause 1 second before sending next character

	      \s	Send a blank character

	      \r	Send a carriage return

	      \b	Send a break character

	      \#	Send the character represented by the octal number
			#.  For example, \05 is CTRL/e.

	      P_ZERO	Change parity from even (default) to zero

	      P_EVEN	Change parity to even

	      P_ODD	     Change parity to odd

	      P_ONE	     Change parity to one parity

	      The  expect2 argument defines another string expected to be read
	      after transmission of the sendspecial  argument  to  the	remote
	      system.

Examples
       In  the	following  example,  the remote system is expected to send the
       string ``login:'', to which the local system replies ``xuucp''.
       login: xuucp ssword: smiley
       Then the word ``ssword:'' is expected from  the	remote	system.	  (The
       first letter of the password prompt varies from system to system, so it
       is safer to look for  the  ending  characters.)	 When  ``ssword:''  is
       received,  the local system sends ``smiley''.  If the login is success‐
       ful, the conversation between  the  peer	 transfer  processes  (uucico)
       begins.	If the login fails, the connection attempt fails.

       In the following example, ``login:'' is expected.
       login:--login xuucp ssword: smiley
       If  it  is received, ``xuucp'' is sent to the remote system.  If login:
       is not received, a carriage return is sent to the  remote  system,  and
       ``login:'' is expected.	If it is received, xuucp is sent to the remote
       system.	The example then proceeds the same as the previous example.

       In the following example, ``login:'' is expected.
       login:-BREAK1-login: xuucp ssword: smiley
       If it is not received, one break sequence is sent to  change  the  baud
       rate  of	 the  remote process.  Then, ``login:'' is again expected, and
       the example proceeds the same as the previous examples.

See Also
       L-dialcodes(5)
       Guide to the uucp Utility

								      L.sys(5)
[top]

List of man pages available for Ultrix

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
...................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net