18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Interrupted system call<br />

Cause<br />

The user issued an interrupt signal (usually Control-c) while the system was in the<br />

middle of executing a system call. When network service is slow, interrupting cd(1)<br />

to a remote-mounted directory can produce this message.<br />

Action<br />

Proceed with your work, this message is purely informational.<br />

Technical Notes<br />

An asynchronous signal (such as interrupt or quit), which a program was set up to<br />

catch, occurred during an internal system call. If execution is resumed after<br />

processing the signal, it will appear as if the interrupted programming function<br />

returned this error condition, so the program might exit with an incorrect error<br />

message.<br />

The symbolic name for this error is EINTR, errno=4.<br />

Invalid argument<br />

Cause<br />

An invalid parameter was specified that the system cannot interpret. For example,<br />

trying to mount an uncreated filesystem, printing without sufficient system support,<br />

or providing an undefined signal to a signal(3C) library function, can all produce<br />

this message.<br />

Action<br />

If you see this message when you are trying to mount a filesystem, make sure that<br />

you have run newfs(1M) to create the filesystem. If you see this message when you<br />

are trying to read a diskette, make sure that the diskette was properly formatted with<br />

fdformat(1), either in DOS format ( pcfs(7FS)) or as a UFS filesystem. If you see<br />

this message while you are trying to print, make sure that the print service is<br />

configured correctly.<br />

90 Solaris Common Messages and Troubleshooting Guide ♦ October, 1998

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

Saved successfully!

Ooh no, something went wrong!