![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Rules & FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| SUN Solaris The Solaris Operating System, usually known simply as Solaris, is a free Unix-based operating system introduced by Sun Microsystems . |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Core dump in HP-UX.. | gyanusoni | UNIX for Dummies Questions & Answers | 0 | 09-07-2007 12:29 AM |
| core dump | sudhir patnaik | UNIX for Advanced & Expert Users | 6 | 05-26-2006 03:03 AM |
| about core dump | zhaohaizhou | High Level Programming | 1 | 09-15-2004 03:30 AM |
| core dump | hassan2 | UNIX for Dummies Questions & Answers | 4 | 05-07-2002 05:05 AM |
| help, what is the difference between core dump and panic dump? | aileen | UNIX for Dummies Questions & Answers | 1 | 06-11-2001 05:08 PM |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Core dump failures
Does anyone have a list of error codes when core dumps fail?
What is error 4? I also have another box that does error-2 occasionally. if anyone has a list of these error codes, it would be appreciated, thanks! I have the error below: NOTICE: core_log: ns-admin[7135] core dump failed, errno=4: /var/core/core_****** |
| Forum Sponsor | ||
|
|
|
||||
|
Using the list above...
No such file or directory The symbolic name for this error is ENOENT, errno=2. ======================================== The specified file or directory does not exist. Either the file name or path name was entered incorrectly. Check the file name and path name for correctness and try again. If the specified file or directory is a symbolic link, it probably points to a nonexistent file or directory. Interrupted system call The symbolic name for this error is EINTR, errno=4. ====================================== The user issued an interrupt signal (usually Control-c) while the system was in the middle of executing a system call. When network service is slow, interrupting cd(1) to a remote-mounted directory can produce this message. Proceed with your work, this message is purely informational. An asynchronous signal (such as interrupt or quit), which a program was set up to catch, occurred during an internal system call. If execution is resumed after processing the signal, it will appear as if the interrupted programming function returned this error condition, so the program might exit with an incorrect error message. |
||||
| Google UNIX.COM |
| Tags |
| inappropriate ioctl for device, stale nfs file handle |
| Thread Tools | |
| Display Modes | |
|
|