10 More Discussions You Might Find Interesting
1. AIX
Hi,
We have 2 lpars on p6 blade. One of the lpar is having 3 core cpu with 5gb memory running sybase as database. An EOD process takes 25 min. to complete.
Now we have an lpar on P7 server with entitled cpu capacity of 2 with 16 Gb memory and sybase as database. The EOD process which takes... (17 Replies)
Discussion started by: vjm
17 Replies
2. UNIX for Dummies Questions & Answers
hi I am having a performance issue with the following requirement
i have to create a permutation and combination on a set of three files
such that each record in each file is picked and the output is redirected in
a specific format but it is taking around 70 odd hours to prepare a
combination... (7 Replies)
Discussion started by: mad_man12
7 Replies
3. AIX
Hi Guys,
This is the situation I am in. Provide your views and input where should I start?
I have one P7 test server and a p520 production server. the job is taking pretty long on the P7 test server when compared to the P5 production server. below is the full detail.
Informix... (5 Replies)
Discussion started by: ithinksgreen
5 Replies
4. Shell Programming and Scripting
Hi All,
I have the following script which I use in Nagios to check the health of the applications, the problem with it is that the curl part ($TOTAL) does not return anything after running for 2-3 hrs, even though from command line the script runs fine but not from Nagios.
There are 17... (1 Reply)
Discussion started by: jacki
1 Replies
5. AIX
Gurus, i have process that runs 5 times a day.
it runs normally (takes about 1 hour) to complete in 3 runs
but it is takes about ( 3 hrs to complete) two times
So i need to figure out why it takes significanlty high time during
those 2 runs.
The process is a shell script that connect to... (2 Replies)
Discussion started by: mad_man12
2 Replies
6. UNIX for Advanced & Expert Users
In my C program i am using very large file(approx 400MB) to read parts of it frequently. But due to large file the performance of the program goes down very badly. It shows very high I/O usage and I/O wait time.
My question is, What are the ways to optimize or tune I/O on linux or how i can get... (10 Replies)
Discussion started by: mavens
10 Replies
7. AIX
Hi All,
I am getting a performance issue in expect5.43.0 library on IBM AIX 5.3. When I have used exp_fexpectv call for pattern matching with the expect string, the execution latency of the call is approximately 200 ms. In that way, I am able to complete only 4 or 5 transactions per... (2 Replies)
Discussion started by: ravindra_maddal
2 Replies
8. Shell Programming and Scripting
I want to read a file.
is it good to use File I/O or shell script??
which one is the best option? (1 Reply)
Discussion started by: vishwaraj
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
on a linux server I have the following :
vmstat 2 10
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
0 4 0 675236 39836 206060 1617660 3 3 3 6 8 7 1 1 ... (1 Reply)
Discussion started by: big123456
1 Replies
10. AIX
We have a AIX v5.3 on a p5 system with a poor performing Ingres database.
We added one CPU to the system to see if this would help. Now there are two CPU's.
with sar and topas -P I see good results: CPU usage around 30%
with topas I only see good results in the process output screen, the... (1 Reply)
Discussion started by: rein
1 Replies
dlclose(3) Library Functions Manual dlclose(3)
NAME
dlclose - Close a dlopen() object
SYNOPSIS
#include <dlfcn.h>
int dlclose(void *handle)
PARAMETERS
A pointer to a global symbol object that is returned from a call to dlopen().
DESCRIPTION
The dlclose function is used to inform the system that the object referenced by a handle returned from a previous dlopen() invocation is no
longer needed by the application.
The use of dlclose() reflects a statement of intent on the part of the process, but does not create any requirements on the dynamic library
loader, such as removal of the code or symbols referenced by handle. Once an object has been closed using dlclose(), an application should
assume that its symbols are no longer available to dlsym(). All objects loaded automatically as a result of invoking dlopen() on the refer-
enced object are also closed.
The dlclose function deallocates the address space for the library corresponding to handle. The results are undefined if any user function
continues to call a symbol resolved in the address space of a library that has since been deallocated by dlclose.
The dlclose operation will not remove an object to which references have been relocated, until or unless all such references are removed.
For instance, an object that had been loaded with a dlopen() operation specifying the RTLD_GLOBAL flag might provide a target for dynamic
relocations performed in the processing of other objects - in such environments, an application may assume that no relocation, once made,
will be undone or remade unless the object requiring the relocation has itself been removed.
RETURN VALUE
If the referenced object was successfully closed, dlclose() returns 0. If the object could not be closed or if handle does not refer to an
open object, dlclose() returns a non-zero value. More detailed diagnostic information will be available through dlerror().
ERRORS
No errors are defined.
NOTES
The dlopen and dlclose routines might dynamically change the resolution of certain symbols referenced by a program or its shared library
dependencies. The dlopen routine might resolve symbols that were previously unresolved, and dlclose might cause resolved symbols to become
unresolved or to be reresolved to a different symbol definition.
A portable application will employ a handle returned from a dlopen() invocation only within a given scope bracketed by the dlopen() and
dlclose() operations. The dynamic library loader is free to use reference counting or other techniques such that multiple calls to
dlopen() referencing the same object may return the same object for handle. The dynamic library loader is also free to re-use a handle. For
these reasons, the value of a handle must be treated as an opaque object by the application, used only in calls to dlsym() and dlclose().
RELATED INFORMATION
dlerror(3), dlopen(3), dlsym(3). delim off
dlclose(3)
