10 More Discussions You Might Find Interesting
1. Red Hat
For instance, root partition is full so I don't need to know about /ABC/XYZ when /ABC/XYZ is a separate mount point. (But /ABC isnt).
Can I run a du command or similar and just look at contents effecting the space on that mount point (/)? (2 Replies)
Discussion started by: psychocandy
2 Replies
2. Red Hat
I have a RHEL 5.3 machine with the following partitions and free space:
Free space on the partitions
/ : 74GB
/boot : 81MB
/var : 73GB
/home : 37GB
/icat : 758MB
/opt : 1.5GB
Now is it possible to allot a free space of some other partitions to /opt? I want around 100 GB more space... (4 Replies)
Discussion started by: omniok
4 Replies
3. Solaris
I added in the configuration file of a whole root zone the following device match entries:
<device match="/dev/rmt/*"/>
<device match="/dev/sg/*"/>
after the reboot the zone was able to see all the devices of its global zone, and let under /dev/rmt and /dev/sg the special files created with... (1 Reply)
Discussion started by: hugo_perez
1 Replies
4. Linux
Hi OS Experts
I would like to increase root partition from another partition so that I can save more documents in Home and Desktop. whether it is possible without formating root partition if so please explain
here is o/p of df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda9... (8 Replies)
Discussion started by: Akshay Hegde
8 Replies
5. Solaris
Version: Solaris 10 (August 2011) on VM
I am kind of new to Solaris.From VM workstation i allocated 35 GB to this Solaris VM's Disk
The disk was named
c1t0d0
Few basic slices for root(8gb), swap(517mb) and /export/home(494mb) were created by the solaris Installer during the... (18 Replies)
Discussion started by: polavan
18 Replies
6. Solaris
hi guys, me again ;)
i recently opened a thread about physical to zone migration.
My zone is mounted over a "bigger" LUN (500GB) and step is now to move the old files, from the physical server, to my zone.
We are talking about 22mio of files.
i used rsync to do that and every time at... (8 Replies)
Discussion started by: beta17
8 Replies
7. Windows & DOS: Issues & Discussions
i have an "old" laptop with 84gb used space, 203gb free, running 32bit Windows Vista.
i've tried all defragmenting programs i could find and though some offer Free Space Defrag, they don't seem to take into account where on the disk to consolidates the space to.
what i am trying to achieve is... (4 Replies)
Discussion started by: Sterist
4 Replies
8. Shell Programming and Scripting
Hello,
I am trying to monitor disk space for each node on the machine. I am able to get all individual nodes but for the '/' node. For example:
df -k:
bash-2.05b# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/xxx 4127108 2415340 1502120 62% /
/dev/yyy ... (3 Replies)
Discussion started by: chiru_h
3 Replies
9. Filesystems, Disks and Memory
hi,
I have a SCO unix server which has a 36gb hard drive, but the IT company who supplied it assigned 1gb to /dev/root, 15mb to /dev/boot and 33gb to /dev/u.
The /dev/root partition is now full, is there a way I can use the 33gb assigned to /dev/u without loosing any data, preferably... (2 Replies)
Discussion started by: Martyn
2 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I've tried to find answer to this question in the forums but i haven't found it.
How can i know the space left in my devices (tape, disk, floppy, etc...)?
It is very important to know at least the free space in the TAPE device.
Can someone help?
Thanx in advance.
Jorge (1 Reply)
Discussion started by: jorge.ferreira
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)