18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

This message can indicate "Result too small" in the case of floating point underflow.<br />

To help pinpoint a program’s math errors, use the matherr(3M) facility.<br />

The symbolic name for this error is ERANGE, errno=34.<br />

rlogin: no directory! connection<br />

closed<br />

Cause<br />

When user tries to remotely login to a machine, he gets the error.<br />

The machine that the customer was trying to rlogin(1) to had permissions of 700<br />

on its root directory. The permissions on root should be 755.<br />

Once the user changed the rootpermissions to 755, he was able to get farther when<br />

attempting a rlogin, but it still failed:<br />

Last login: Fri Aug 29 10:24:43 from machinename<br />

no shell<br />

connection closed<br />

Action<br />

The machine that the user was trying to rlogin into had the permissions set to 700 on<br />

both the root and /usr/bin directories. For both directories, the permissions<br />

should be 775. Once the user changed the permissions to 775, rlogin(1) was<br />

successful.<br />

Another possibility is to check the user’s >passwd(1) entry in the NIS/NIS+ map. A<br />

login shell such as /usr/dist/exe/tcsh or /net/lab/.../csh could cause the<br />

failure because of NFS mount permission.<br />

Alphabetical Message Listing 163

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!