10 More Discussions You Might Find Interesting
1. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
2. Shell Programming and Scripting
Hi ,
I Have following requirement:
DB2 Sql query to pass from a parameter file
for example, I would create a parameter file with (SELECT column 1, column 2 FROM Table name) then job would read it and create a file with the contents named table.txt
How to write/modify below ksh script to... (10 Replies)
Discussion started by: developer.dwh9
10 Replies
3. Shell Programming and Scripting
hi,
I work on oracel 10g unix system.
I need to unload data from few tables to a unl file using shell script. I've a file which contains the list of tables. The shell has to refer to this list and create a unl for each table.
Table_list.txt
table1|
table2|
table3|
has to... (1 Reply)
Discussion started by: dvah
1 Replies
4. UNIX and Linux Applications
:)hi,
i work with ids and i've got a task now to load some data from oracle table to ids table. I'm trying to unload data from oracel tables.
I use UNLOAD TO <filename> SELECT * FROM <table1>; sql in IDS to unload data to a unl. Is there a equivalent sql in oracle? Or is there any... (0 Replies)
Discussion started by: divak
0 Replies
5. Shell Programming and Scripting
Hey, I am working on some file comparisons with csv files. csv files use "," as the field separator and I want to do a
cat -n file > file
to put the file numbers at the beginning of the lines, but cat uses "\t" as the separator. Can I force cat to use "," as the Output file separator. Or can... (15 Replies)
Discussion started by: MHardeman25
15 Replies
6. Shell Programming and Scripting
Hello,
I am using suse 10.1 and isql from unixodbc to connect to a MS SQL server. I got everything to work fine. What do I need to unload the results from the sql to a file? I attempted to put unload to in my sql statement but got a error. I don't see in the isql help where it has a option to... (0 Replies)
Discussion started by: benefactr
0 Replies
7. Red Hat
Hi,
This may be a dumb question, but here goes. While I have been using Linux for some time, I am wondering if a certain capability exists within Red Hat that I have found within SUSE.
Cool stuff you might not know that AutoYast can do ? Part 1 Linux In Novell’s East Region
points to... (0 Replies)
Discussion started by: mark54g
0 Replies
8. HP-UX
Hello,
yeah... here my question :
Exist some way to force umount on HP other than reboot?
Thanks
gb (12 Replies)
Discussion started by: gogol_bordello
12 Replies
9. HP-UX
sorry, wrong section, mod please close thread (0 Replies)
Discussion started by: robertngo
0 Replies
10. Shell Programming and Scripting
Hi,
I just wonder why the unload tools from INFORMIX doesn't unload all required file to every output of mOutFile at the accumulative way OR my script has an error ? In fact it just unload to one single record at the latest.
for mFile in x???
do
echo "Now working with file "$mFile"... (1 Reply)
Discussion started by: cedrichiu
1 Replies
dlclose(3C) Standard C Library Functions dlclose(3C)
NAME
dlclose - close a shared object
SYNOPSIS
#include <dlfcn.h>
int dlclose(void *handle);
DESCRIPTION
The dlclose() function decrements the reference count of the supplied handle. This handle represents an executable object file and its
dependencies, acquired from a previous call to dlopen(). A handle that is no longer referenced is processed in an attempt to unload any
objects that are associated with the handle from the current process. An unreferenced handle is no longer available to dlsym().
Any finalization code within an object is executed prior to that object being unloaded. Any routines registered by an object using
atexit(3C) are called prior to that object being unloaded. See NOTES.
RETURN VALUES
If the handle was successfully unreferenced, dlclose() returns 0. If the handle is invalid, or an error occurred as a result of unloading
an object, dlclose() returns a non-zero value. Additional diagnostic information is available through dlerror().
USAGE
The dlclose() function is one of a family of functions that give the user direct access to the dynamic linking facilities. These facilities
are available to dynamically-linked processes only. See the Linker and Libraries Guide.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
ld(1), ld.so.1(1), atexit(3C), dladdr(3C), dldump(3C), dlerror(3C), dlopen(3C), dlsym(3C), attributes(5), standards(5)
Linker and Libraries Guide
NOTES
A successful invocation of dlclose() does not guarantee that the objects associated with the handle are removed from the address space of
the current process. Objects can be referenced by multiple handles, or by other objects. An object is not removed from the address space
of the current process until all references to that object are removed.
Once an object has been closed by dlclose(), referencing symbols contained in that object can cause undefined behavior.
As part of unloading an object, finalization code within the object is called before the dlclose() returns. This finalization is user code,
and as such, can produce errors that can not be caught by dlclose(). For example, an object loaded using RTLD_LAZY that attempts to call a
function that can not be located, results in process termination. Erroneous programming practices within the finalization code can also
result in process termination. The runtime linkers debugging facility can offer help identifying these types of error. See the LD_DEBUG
environment variable of ld.so.1(1).
SunOS 5.10 1 March 2004 dlclose(3C)