ring (5) --- network communication server 09/18/84 | _U_s_a_g_e | ring | _D_e_s_c_r_i_p_t_i_o_n | 'Ring' is a network communication server for Prime com- | puters. When run as a privileged process on a node of the | ringnet, it figures out who it is and who all the other | nodes are, and then procedes to connect itself in a ring | with its predecessor and successor using virtual circuits. | Once connected, it will (currently) accept requests from | users to execute commands on a legal remote node and pass | the status back to the user. It also ensures that the | system time (time of day, and date) is consistent among all | the machines in the network. | 'Ring' is unfinished but has many possibilities. The plans | before the SWT project ended and its creator found another | job were to set up a method for load sharing among computers | in a network under the Software Tools Subsystem. The idea | was to make a "/dev/net" device that would have its port | number returned by a port server ('ring', or course) on the | remote system. A shell would be cranked up on the remote | system who's standard input would be a NET device. The | source of the NET device would be the system where the user | actually resided. This would allow the user (only under the | Subsystem) to communicate with his process remotely. | _M_e_s_s_a_g_e_s | Numerous. Sorry, but see the source code. | _B_u_g_s | Simply unfinished. Has tremendous possibilities. | _S_e_e _A_l_s_o | broadcast (3), execute (3), setime (3), _R_i_n_g _-_- _T_h_e _S_o_f_t_w_a_r_e | _T_o_o_l_s _S_u_b_s_y_s_t_e_m _N_e_t_w_o_r_k _U_t_i_l_i_t_y ring (5) - 1 - ring (5)