03-21-2008
You don't need patches. You need to either a) install the C libraries package -sunfreeware.com has a package that you can install with pkgadd; or b) the library may be installed, but not in your path.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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
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
Hi all,
when am rebooting the server (SF v890) we are facing
"open boot diagnostic failed".
Thanks in Adv. (5 Replies)
Discussion started by: arjunreddy3
5 Replies
4. Solaris
Hi all.
I try to start an application, but libucb.so1 is missing.
# appl23
# appl23ld.so.1: appl23: fatal: libucb.so1: open failed: No such file or directory
killed
#
# ldd appl23
libXm.so.3 => /usr/lib/libXm.so.3
libMrm.so.3 => /usr/lib/libMrm.so.3
... (14 Replies)
Discussion started by: wolfgang
14 Replies
5. Programming
Hello,
I want to migrate from application that was compiled with Sun 4.2 compiler with C++ standard library(libCstd.so.1) to STLport(libstlport.so.1) library.
I am able to compile all the files on Solaris 10 with Sun 5.8 compiler but linking is failing with symbol referencing errors though... (0 Replies)
Discussion started by: shafi2all
0 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I have try to ndm to one server to another server. but i am getting this error. what is this error? are files not in source folder?
Source file open failed. Error= 2
Regards,
Balamurgan (1 Reply)
Discussion started by: krbala1985
1 Replies
7. Red Hat
Hi,
# yum --skip-broken -y update
rpmdb: Thread/process 6657/3078387392 failed: Thread died in Berkeley DB library
error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 - (-30974)
error: cannot open... (3 Replies)
Discussion started by: sef alislam
3 Replies
8. Solaris
Hey for some reason I think I deleted a critical file for sendmail. I was looking the log file on /var/log/cron for cron, and the file isn't there and I found out the reason why is because I'm missing libssl.so.0.9.7. Im running Solaris 11.
I checked smtp and got the following:
#svcs -xv... (3 Replies)
Discussion started by: picolin
3 Replies
9. UNIX for Beginners Questions & Answers
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
10. Shell Programming and Scripting
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
LEARN ABOUT FREEBSD
kvm_open
KVM_OPEN(3) BSD Library Functions Manual KVM_OPEN(3)
NAME
kvm_open, kvm_openfiles, kvm_close -- initialize kernel virtual memory access
LIBRARY
Kernel Data Access Library (libkvm, -lkvm)
SYNOPSIS
#include <fcntl.h>
#include <kvm.h>
kvm_t *
kvm_open(const char *execfile, const char *corefile, const char *swapfile, int flags, const char *errstr);
kvm_t *
kvm_openfiles(const char *execfile, const char *corefile, const char *swapfile, int flags, char *errbuf);
int
kvm_close(kvm_t *kd);
DESCRIPTION
The functions kvm_open() and kvm_openfiles() return a descriptor used to access kernel virtual memory via the kvm(3) library routines. Both
active kernels and crash dumps are accessible through this interface.
The execfile argument is the executable image of the kernel being examined. This file must contain a symbol table. If this argument is
NULL, the currently running system is assumed, as determined from getbootfile(3).
The corefile argument is the kernel memory device file. It can be either /dev/mem or a crash dump core generated by savecore(8). If
corefile is NULL, the default indicated by _PATH_MEM from <paths.h> is used. It can also be set to a special value /dev/null by utilities
like ps(1) that do not directly access kernel memory.
The swapfile argument is currently unused.
The flags argument indicates read/write access as in open(2) and applies only to the core file. Only O_RDONLY, O_WRONLY, and O_RDWR are per-
mitted.
There are two open routines which differ only with respect to the error mechanism. One provides backward compatibility with the SunOS kvm
library, while the other provides an improved error reporting framework.
The kvm_open() function is the Sun kvm compatible open call. Here, the errstr argument indicates how errors should be handled. If it is
NULL, no errors are reported and the application cannot know the specific nature of the failed kvm call. If it is not NULL, errors are
printed to stderr with errstr prepended to the message, as in perror(3). Normally, the name of the program is used here. The string is
assumed to persist at least until the corresponding kvm_close() call.
The kvm_openfiles() function provides BSD style error reporting. Here, error messages are not printed out by the library. Instead, the
application obtains the error message corresponding to the most recent kvm library call using kvm_geterr() (see kvm_geterr(3)). The results
are undefined if the most recent kvm call did not produce an error. Since kvm_geterr() requires a kvm descriptor, but the open routines
return NULL on failure, kvm_geterr() cannot be used to get the error message if open fails. Thus, kvm_openfiles() will place any error mes-
sage in the errbuf argument. This buffer should be _POSIX2_LINE_MAX characters large (from <limits.h>).
RETURN VALUES
The kvm_open() and kvm_openfiles() functions both return a descriptor to be used in all subsequent kvm library calls. The library is fully
re-entrant. On failure, NULL is returned, in which case kvm_openfiles() writes the error message into errbuf.
The kvm_close() function returns 0 on success and -1 on failure.
SEE ALSO
open(2), kvm(3), kvm_getargv(3), kvm_getenvv(3), kvm_geterr(3), kvm_getprocs(3), kvm_nlist(3), kvm_read(3), kvm_write(3), kmem(4), mem(4)
BUGS
There should not be two open calls. The ill-defined error semantics of the Sun library and the desire to have a backward-compatible library
for BSD left little choice.
BSD
January 29, 2004 BSD