Technical Notes

A known problem exists with starting hundreds of rsh(1) processes on another machine. This message appears because rsh(1) hangs while binding to a reserved port and responds too slowly to interact with the network naming service.