where:

-T tcp specifies the transport that the service uses.

hostname is the name of the machine where the service is running.

If the service is not running, this message is displayed:

rpcinfo: RPC: Program not registered

If you see this message, it is possible that the /etc/nsswitch.conf services: entry is incorrectly configured. See “Checking the /etc/nsswitch.conf File” on page 8.

netstat

This messages shows that the service is running:

# netstat -agrep rdc

 

 

 

 

*.rdc

*.*

0

0 65535

0

LISTEN

*.rdc

*.*

0

0 65535

0

LISTEN

*.rdc

*.*

 

 

0

0

65535

0 LISTEN

 

 

 

 

 

 

 

 

 

 

If the /dev/rdc Link Is Not Created

Note – Although other applications make entries in the files described in this section, you can edit the files to correct these problems. Always make a backup copy of a file before editing it.

The /dev/rdc pseudo-link might not be created for the following reasons:

The /etc/devlink.tab file is missing an entry for the /dev/rdc pseudo-link. This example shows a valid entry:

#grep rdc /etc/devlink.tab

type=ddi_pseudo;name=rdc \D

Chapter 2 Remote Mirror Software Troubleshooting Tips 9

Page 19
Image 19
Sun Microsystems 3.2 manual If the /dev/rdc Link Is Not Created

3.2 specifications

Sun Microsystems 3.2, often referred to as SunOS 3.2, was a notable release of the Sun operating system that emerged during the rapidly evolving landscape of computer technology in the early 1980s. This operating platform was designed specifically for Sun Workstations, utilizing the robust hardware architecture developed by Sun Microsystems. The introduction of SunOS 3.2 marked a significant step forward in the development of UNIX-like operating systems optimized for entrepreneurship and scientific applications.

One of the main features of SunOS 3.2 was its adherence to the Berkeley Software Distribution (BSD) model, which allowed for advanced networking capabilities, enhanced performance, and efficient resource management. BSD's influence provided SunOS 3.2 with TCP/IP networking protocols, allowing users to connect to other devices seamlessly and manage network resources easily. This feature was crucial during a time when networking was becoming increasingly vital for organizations.

The system's support for virtual memory was another innovative characteristic. SunOS 3.2 utilized demand paging, which allowed programs to use more memory than was physically installed on their machines, significantly improving multitasking and overall system responsiveness. This capability was particularly advantageous for enterprises that relied on large-scale computations and data analysis.

SunOS 3.2 also introduced support for the Sun Window System, which meant users could utilize graphical user interfaces for interacting with applications, moving away from purely text-based command interfaces. This transition paved the way for more intuitive user experiences in the realm of computing, making powerful UNIX capabilities more accessible.

The inclusion of software utilities such as the C shell (csh) and a variety of development tools further strengthened SunOS 3.2’s position as a suitable platform for developers. The system provided robust development environments for programming in languages like C and assembly, catering to custom application requirements across different industries.

Lastly, security features were integrated into SunOS 3.2 to safeguard sensitive data and enhance system integrity. Permission settings and user authentication mechanisms were refined, allowing organizations to securely manage their computing resources.

In summary, SunOS 3.2 represented a landmark evolution in operating systems, showcasing a blend of advanced networking, memory management, graphical user interface, development tools, and security—elements that defined a generation of computing within the high-performance ecosystem of Sun Microsystems.