Part I Network Services Topics
Part II Accessing Network File Systems Topics
4. Managing Network File Systems (Overview)
5. Network File System Administration (Tasks)
6. Accessing Network File Systems (Reference)
8. Planning and Enabling SLP (Tasks)
10. Incorporating Legacy Services
Part V Serial Networking Topics
15. Solaris PPP 4.0 (Overview)
16. Planning for the PPP Link (Tasks)
17. Setting Up a Dial-up PPP Link (Tasks)
18. Setting Up a Leased-Line PPP Link (Tasks)
19. Setting Up PPP Authentication (Tasks)
20. Setting Up a PPPoE Tunnel (Tasks)
21. Fixing Common PPP Problems (Tasks)
22. Solaris PPP 4.0 (Reference)
23. Migrating From Asynchronous Solaris PPP to Solaris PPP 4.0 (Tasks)
25. Administering UUCP (Tasks)
System-Name Field in /etc/uucp/Systems File
Time Field in /etc/uucp/Systems File
Type Field in /etc/uucp/Systems File
Speed Field in /etc/uucp/Systems File
Phone Field in /etc/uucp/Systems File
Chat-Script Field in /etc/uucp/Systems File
Enabling Dialback Through the Chat Script
Hardware Flow Control in /etc/uucp/Systems File
Setting Parity in /etc/uucp/Systems File
Type Field in /etc/uucp/Devices File
Type Fields in Devices File and Systems File
Line Field in the /etc/uucp/Devices File
Line2 Field in the /etc/uucp/Devices File
Class Field in the /etc/uucp/Devices File
Dialer-Token-Pairs Field in the /etc/uucp/Devices File
Structure of the Dialer-Token-Pairs Field in the /etc/uucp/Devices File
Protocol Definitions in /etc/uucp/Devices File
Enabling Hardware Flow Control in the /etc/uucp/Dialers File
Setting Parity in the /etc/uucp/Dialers File
Other Basic UUCP Configuration Files
UUCP /etc/uucp/Permissions File
UUCP NOREAD and NOWRITE Options
Combining MACHINE and LOGNAME Entries for UUCP
Relationship Between User and System Job Grades
Part VI Working With Remote Systems Topics
27. Working With Remote Systems (Overview)
28. Administering the FTP Server (Tasks)
29. Accessing Remote Systems (Tasks)
Part VII Monitoring Network Services Topics
This section describes three less-frequently modified files that impact the use of UUCP facilities.
The /etc/uucp/Devconfig file enables you to configure devices by service, such as uucp or cu. Devconfig entries define the STREAMS modules that are used for a particular device. These entries have the following format:
service=x device=y push=z[:z...]
x can be cu, uucico, or both services separated by a colon. y is the name of a network and must match an entry in the Devices file. z is replaced by the names of STREAMS modules in the order that they are to be pushed onto the Stream. Different modules and devices can be defined for cu and uucp services.
The following entries are for a STARLAN network and would most commonly be used in the file:
service=cu device=STARLAN push=ntty:tirdwr service=uucico device=STARLAN push=ntty:tirdwr
This example pushes ntty, then tirdwr.
The /etc/uucp/Limits file controls the maximum number of simultaneous uucicos, uuxqts, and uuscheds that are running in the uucp networking. In most situations, the default values are acceptable and no changes are needed. If you want to change them, however, use any text editor.
The format of the Limits file is as follows:
service=x max=y:
x can be uucico, uuxqt or uusched, and y is the limit that is permitted for that service. The fields can be in any order and in lowercase.
The following entries should most commonly be used in the Limits file:
service=uucico max=5 service=uuxqt max=5 service=uusched max=2
The example allows five uucicos, five uuxqts, and two uuscheds to run on your machine.
The other file that affects the use of communication facilities is the remote.unknown file. This file is a binary program that executes when a machine that is not found when any of the Systems files starts a conversation. This program logs the conversation attempt and drops the connection.
![]() | Caution - If you change the permissions of the remote.unknown file so that the file cannot execute, your system accepts connections from any system. |
This program executes when a machine that is not in any of the Systems starts a conversation. The program logs the conversation attempt but fails to make a connection. If you change the permissions of this file so that the file cannot execute (chmod 000 remote.unknown), your system accepts any conversation requests. This change is not trivial. You should have good reasons for making this change.