Sponsored Content
Top Forums UNIX for Dummies Questions & Answers NDM: Source file open failed. Error= 2 Post 302518413 by DGPickett on Friday 29th of April 2011 02:31:13 PM
Old 04-29-2011
2 is ENOENT, no such (see man errno or man 2 open() for the errno values and meanings). You got it, no file in source dir, or no source dir!
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Failed to open output file Error

Hi guys, I Have written a script,In that it will call another file which contains the sql quaries. while wxecuting that I am getting the below exception 01/16|06:28:06:16800: Operating System Error|Failed to open output file Can anybody help me about this,,Its urgent (0 Replies)
Discussion started by: Anji
0 Replies

2. Solaris

Error:: libm.so.2:open failed

Hi, I am working with solaris 9 and I want to install perforce on that,so I downloaded the p4v.bin file and try to install it by the command ./p4v after that it is giving the error--- ld.so.1: ./p4v.bin: fatal: libm.so.2: open failed: No such file or directory Killed I am not... (3 Replies)
Discussion started by: smartgupta
3 Replies

3. Solaris

Error- ld.so.1: expr: fatal: libgmp.so.3: open failed:No such file or directory

Hi Friends I have a compiler(Sun Forte,I believe) running in my Solaris 9 box. since y'day my development team is finding this error when they compile: ld.so.1: expr: fatal: libgmp.so.3: open failed: No such file or directory I ran a search for this file and found it in one of my file... (2 Replies)
Discussion started by: Hari_Ganesh
2 Replies

4. Red Hat

"ERROR : failed to mount nfs source" Red Hat Kickstart

Hi There, I have been googling for this error and try solution provided but still not avail to resolve Kickstart Issue. Any expert have encounter this problem? Thanks. Regards, Regmaster (4 Replies)
Discussion started by: regmaster
4 Replies

5. Solaris

./curl -V showing fatal: libldap.so.5: open failed: No such file or directory

Hi Guys, I am facing this Error bash-2.03$ ./curl -V ld.so.1: curl: fatal: libldap.so.5: open failed: No such file or directory Killed bash-2.03$ while executing ./curl -V in /opt/sfw/bin directory. I am using Sun Solaris 10. which package upgrage can give me this missing... (9 Replies)
Discussion started by: manalisharmabe
9 Replies

6. Infrastructure Monitoring

Puppet open source ERROR 400

Hi! I' have 2 files: file test.pp class copy { file {"/etc/puppet/files/client1/testfile": path => "/home/vassiliy/mytestfile", source => "puppet:///mpoint/client1/testfile", mode => '644' } and file site.pp import "test.pp" node client1 { include copy } in fileserver.conf (0 Replies)
Discussion started by: vvz
0 Replies

7. UNIX for Beginners Questions & Answers

Rdesktop - ERROR: Failed to open keymap en-us

I just updated my rdesktop to 1.8.3 from source ( on Slackware 11 ) and had troubles with arrow keys/page up/page down not working. I see this on the console: ERROR: Failed to open keymap en-us The fix is a permission change. I initially looked at /usr/share/rdesktop/keymaps and everything... (1 Reply)
Discussion started by: agentrnge
1 Replies

8. Shell Programming and Scripting

Linux open failed: No such file or directory error

Hi, The below commands works fine on serverB . /etc/profile; cd /export/home/user2/utils/plugin/ ./runme.shHowever, when i run the same commands from serverA it fails $ ssh -q user2@serverB ". /etc/profile; cd /export/home/user2/utils/plugin; ./runme.sh"Output Error: Please find the below... (8 Replies)
Discussion started by: mohtashims
8 Replies

9. Shell Programming and Scripting

Script to find Error: rpmdb open failed on list of servers

Hello all, I have a task to patch red hat servers and some servers have a corrupted rpm database and return the error: Error: rpmdb open failed I know how to fix this when it occurs. What I'm hoping to do is scan a list of servers by IP and report back which server have this error. ... (6 Replies)
Discussion started by: greavette
6 Replies
explain_closedir(3)					     Library Functions Manual					       explain_closedir(3)

NAME
explain_closedir - explain closedir(3) errors SYNOPSIS
#include <libexplain/closedir.h> const char *explain_closedir(DIR *dir); const char *explain_errno_closedir(int errnum, DIR *dir); void explain_message_closedir(char *message, int message_size, DIR *dir); void explain_message_errno_closedir(char *message, int message_size, int errnum, DIR *dir); DESCRIPTION
These functions may be used to obtain explanations for errors returned by the closedir(3) system call. explain_closedir const char *explain_closedir(DIR *dir); The explain_closedir function is used to obtain an explanation of an error returned by the closedir(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: if (closedir(dir) < 0) { fprintf(stderr, "%s ", explain_closedir(dir)); exit(EXIT_FAILURE); } dir The original dir, exactly as passed to the closedir(3) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_errno_closedir const char *explain_errno_closedir(int errnum, DIR *dir); The explain_errno_closedir function is used to obtain an explanation of an error returned by the closedir(3) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (closedir(dir) < 0) { int err = errno; fprintf(stderr, "%s ", explain_errno_closedir(err, dir)); exit(EXIT_FAILURE); } errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. dir The original dir, exactly as passed to the closedir(3) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_message_closedir void explain_message_closedir(char *message, int message_size, DIR *dir); The explain_message_closedir function may be used to obtain an explanation of an error returned by the closedir(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: if (closedir(dir) < 0) { char message[3000]; explain_message_closedir(message, sizeof(message), dir); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. dir The original dir, exactly as passed to the closedir(3) system call. explain_message_errno_closedir void explain_message_errno_closedir(char *message, int message_size, int errnum, DIR *dir); The explain_message_errno_closedir function may be used to obtain an explanation of an error returned by the closedir(3) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (closedir(dir) < 0) { int err = errno; char message[3000]; explain_message_errno_closedir(message, sizeof(message), err, dir); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. dir The original dir, exactly as passed to the closedir(3) system call. SEE ALSO
closedir(3) close a directory explain_closedir_or_die(3) close a directory and report errors COPYRIGHT
libexplain version 0.52 Copyright (C) 2008 Peter Miller explain_closedir(3)
All times are GMT -4. The time now is 03:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy