02-27-2006
leet speek is hard to read.
It looks like you are describing shared libraries - the $TEXT segment is mapped publicly so that any process using the library uses the same $TEXT segment in memory.
I don't get what inodes have to do with it.... shared files do have inodes, but dld works with symbols and entry points. Not inodes.
10 More Discussions You Might Find Interesting
1. Solaris
hiho,
i would like to show my apprentices the auto-defrag/perform mechanism from UFS. new FS, creating new directories, each directory get its own cylinder on the disk. hmm....
they want proofs.....
*embarrassing*
i couldn't remember how to look on which block the inode is linked....
so,... (4 Replies)
Discussion started by: pressy
4 Replies
2. Red Hat
hi,
can anyone please tell me where i can extract inode numbers and path associated with all file descriptors. i want these informations only. is there any system call or functions to get these things? i hav a RHEL 4. also /proc/pid/fd shows some file descriptor list. is that the proper path to... (1 Reply)
Discussion started by: sanjaykhuntia
1 Replies
3. UNIX for Dummies Questions & Answers
Dear Friend ,
what is incore inode ? and
what is difference between incore inode and inode ?????
sanjay (1 Reply)
Discussion started by: sanjaygoyan
1 Replies
4. Solaris
how can i see inode table information of a perticler inode.anybody knows pls tell me.
Than.Q (3 Replies)
Discussion started by: nag.mi2000
3 Replies
5. AIX
Hi Guys,
I have this filesystem got big with inode:
/dev/hd4 3670016 183664 95% 63705 58% /var
I don't know why the system doesn't give alerts on this FS although it's 95% and why the inode is 58%.
Any comments will be highly appreciated.
Thanks,
itik (1 Reply)
Discussion started by: itik
1 Replies
6. UNIX for Dummies Questions & Answers
can someone please tell me why is the filename not inlcuded in the inode of the file? (2 Replies)
Discussion started by: wowman
2 Replies
7. Homework & Coursework Questions
usually there are no free inode whose number is less than remembered inode but exception are there..tell me those exception (4 Replies)
Discussion started by: pk_mal
4 Replies
8. Solaris
Inode usage on one of my servers is up to 85%
Whats the best way of finding which directories are storing loads of files? (1 Reply)
Discussion started by: JayC89
1 Replies
9. Solaris
Dear,
How can i check inode information in my Solaris box?
With Regards,
Mjoshi (4 Replies)
Discussion started by: mjoshi87
4 Replies
10. UNIX for Dummies Questions & Answers
Environment: O.S Version HP-UX B.11.31 U ia64
What is the recommended Inode free nodes?
On our server Unix Sys Admin, have setup warning email alert when % of I-node usage is above or equal at 5%.
Sample Email:
---------------------------------------------------
Subject: WARNING:... (6 Replies)
Discussion started by: Siva SQL
6 Replies
LEARN ABOUT OPENDARWIN
shmget
SHMGET(2) BSD System Calls Manual SHMGET(2)
NAME
shmget -- get shared memory area identifier
SYNOPSIS
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
int
shmget(key_t key, int size, int shmflg);
DESCRIPTION
shmget() returns the shared memory identifier associated with the key key.
A shared memory segment is created if either key is equal to IPC_PRIVATE, or key does not have a shared memory segment identifier associated
with it, and the IPC_CREAT bit is set in shmflg.
If a new shared memory segment is created, the data structure associated with it (the shmid_ds structure, see shmctl(2)) is initialized as
follows:
o shm_perm.cuid and shm_perm.uid are set to the effective uid of the calling process.
o shm_perm.gid and shm_perm.cgid are set to the effective gid of the calling process.
o shm_perm.mode is set to the lower 9 bits of shmflg.
o shm_lpid, shm_nattch, shm_atime, and shm_dtime are set to 0
o shm_ctime is set to the current time.
o shm_segsz is set to the value of size.
RETURN VALUES
Upon successful completion a positive shared memory segment identifier is returned. Otherwise, -1 is returned and the global variable errno
is set to indicate the error.
ERRORS
[EACESS] A shared memory segment is already associated with key and the caller has no permission to access it.
[EEXIST] Both IPC_CREAT and IPC_EXCL are set in shmflg, and a shared memory segment is already associated with key.
[ENOSPC] A new shared memory indentifier could not be created because the system limit for the number of shared memory identifiers
has been reached.
[ENOENT] IPC_CREAT was not set in shmflg and no shared memory segment associated with key was found.
[ENOMEM] There is not enough memory left to created a shared memory segment of the requested size.
SEE ALSO
shmctl(2), shmat(2), shmdt(2)
BSD
August 17, 1995 BSD