DNSUPP Support


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users DNSUPP Support
# 1  
Old 11-19-2008
DNSUPP Support

Hi,

Could anyone explain the term "DNSUPP" and what does it stand for? And something about Multi-Casting and "lower level" in UNIX.

Your help would be highly appreciated,

Thanks,

Shiraz
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. HP-UX

hp-ux support merced

hi all ! does anyone know what version hp-ux support VLIW Itanium (Merced) 733Mhz? thanks (2 Replies)
Discussion started by: ijj
2 Replies

2. Solaris

Levels of support

Hello, I have a simple question because I can not find the information at oracle.com I want to buy support for OS Solaris and Servers hardware. I need information what are the levels of support and how much they cost? I need a help. Have a nice day (3 Replies)
Discussion started by: bieszczaders
3 Replies

3. SuSE

openSUSE support

does Novell support openSUSE as it does for it's server packages, or is openSUSE's support the same as every other distribution of linux? (1 Reply)
Discussion started by: bcbotha
1 Replies

4. AIX

Phone support

We have a 7028 p series server that has a lapsed hardware service contract, and I was attempting to create a billable tech support phone call, and IBM said that they do on site billable only. Is anybody out there aware of reputable third party support companies I might be able to contact. I have... (7 Replies)
Discussion started by: markper
7 Replies

5. UNIX for Dummies Questions & Answers

Ntfs support

hello, I want to acces my other drives(NTFS) on my fedora 6......I had recomplied my kernel to 2.6.23....previously it was 2.6.18.... Also I had loaded driver for ntfs ie.......installed successfully ....fuse + ntfs-3g..... Now I am able to accces my other ntfs drives....... but what i need is... (11 Replies)
Discussion started by: arunchaudhary19
11 Replies

6. Solaris

DLT8000 Support in 2.5.1

Hi Guys, Old OS I know, but does anyone know the patch number (if indeed it is a patch) or know where I can get the drivers to get a HP DLT8000 working under Solaris 2.5.1. Any help, advice (other than upgrade :) ) appreciated. Thanks Marty (0 Replies)
Discussion started by: callmebob
0 Replies

7. Solaris

need to generate support id..

Hi, we bought a new sun ultra 45 workstation preloaded with solaris 10. Now i need to download the latest patch cluster from sunsolve. But it is asking for a valid service plan. Anybody can help how to generate a support id.. (2 Replies)
Discussion started by: sriram.s
2 Replies

8. UNIX for Advanced & Expert Users

sata support

i have a system which has two hard disks..one is sata and the other one is normal ata hard disk. i wish to install red hat enterprise linux WS(desktop edition) on my sata hard disk..but the installer shows me only my ata hard disk.. i searched the net..it says that a library-- libata will let it... (2 Replies)
Discussion started by: ankit.jss
2 Replies

9. UNIX for Dummies Questions & Answers

XML support

Does Unix or Linux support XML (1 Reply)
Discussion started by: usha4u
1 Replies

10. HP-UX

HP Support Plus media

Hi folks, i owe a HP 9000 E55 (antique...) server. I also owe the original version of the OS HPUX 11.0. Unfortenately i can't find the HP-Support Plus medium. During the instlallation i was asked to put it in, i always skip this one. But the system runs not very well. On HP's website you can... (8 Replies)
Discussion started by: FNORD
8 Replies
Login or Register to Ask a Question
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)