11-15-2006
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.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Dummies Questions & Answers
does any one have read a core dump?
is there any reader for that? or may i know what is the use of that core which takes sometimes memory in GBs?
:) (6 Replies)
Discussion started by: sskb
6 Replies
3. UNIX for Dummies Questions & Answers
I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start
but savecore failed to create the two files, that is vmcore.n and vmunix.n.
savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname
1)... (4 Replies)
Discussion started by: hassan2
4 Replies
4. Programming
MY friends:
my program under sco unix have a problem?
it create a core dump file on the path when execute program ,
but i can't find the error of the C program ,i don't know how to
see the error about my program use core, please help me
or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies
5. UNIX for Dummies Questions & Answers
Hi All
I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
Discussion started by: gyanusoni
0 Replies
6. UNIX for Advanced & Expert Users
Hello all,
Iam new to unix while executing java program which finely working in windows know iam testing with unix ,but in unix while executing iam getting core dump, my application is in client server environment and it is menu drivrn application on clicking options no problem but after some time... (1 Reply)
Discussion started by: vinp
1 Replies
7. AIX
My application gives core dump. When i am debugging with dbx getting instructions below:
pthdb_session.c, 818: 695445 PTHDB_INTERNAL (internal error)
pthreaded.c, 1941: PTHDB_INTERNAL (internal error)
Illegal instruction (illegal opcode) in . at 0x0
warning: Unable to access address 0x0... (1 Reply)
Discussion started by: bapi
1 Replies
8. Programming
how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies
9. UNIX for Dummies Questions & Answers
my progrme complaints 'Segmentation fault'.
How to let it print 'Segmentation fault(core dumped)' and generate core dump file?
$ulimit
unlimited (22 Replies)
Discussion started by: vistastar
22 Replies
10. HP-UX
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Discussion started by: messi777
1 Replies
LEARN ABOUT NETBSD
symlink
SYMLINK(2) BSD System Calls Manual SYMLINK(2)
NAME
symlink -- make symbolic link to a file
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
symlink(const char *name1, const char *name2);
DESCRIPTION
A symbolic link name2 is created to name1 (name2 is the name of the file created, name1 is the string used in creating the symbolic link).
Either name may be an arbitrary path name; the files need neither to be on the same file system nor to exist.
RETURN VALUES
Upon successful completion, a zero value is returned. If an error occurs, the error code is stored in errno and a -1 value is returned.
ERRORS
The symbolic link succeeds unless:
[ENOTDIR] A component of the name2 prefix is not a directory.
[ENAMETOOLONG] A component of a pathname exceeded {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} characters.
[ENOENT] A component of the name2 path does not exist.
[EACCES] A component of the name2 path prefix denies search permission.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[EEXIST] name2 already exists.
[EIO] An I/O error occurred while making the directory entry for name2, or allocating the inode for name2, or writing out the
link contents of name2.
[EROFS] The file name2 would reside on a read-only file system.
[ENOSPC] The directory in which the entry for the new symbolic link is being placed cannot be extended because there is no space
left on the file system containing the directory.
[ENOSPC] The new symbolic link cannot be created because there there is no space left on the file system that will contain the sym-
bolic link.
[ENOSPC] There are no free inodes on the file system on which the symbolic link is being created.
[EDQUOT] The directory in which the entry for the new symbolic link is being placed cannot be extended because the user's quota of
disk blocks on the file system containing the directory has been exhausted.
[EDQUOT] The new symbolic link cannot be created because the user's quota of disk blocks on the file system that will contain the
symbolic link has been exhausted.
[EDQUOT] The user's quota of inodes on the file system on which the symbolic link is being created has been exhausted.
[EIO] An I/O error occurred while making the directory entry or allocating the inode.
[EFAULT] name1 or name2 points outside the process's allocated address space.
SEE ALSO
ln(1), link(2), readlink(2), unlink(2), symlink(7)
HISTORY
The symlink() function call appeared in 4.2BSD.
BSD
June 4, 1993 BSD