Complete list of process attributes?

From: Marc Rochkind (rochkind_at_basepath.com)
Date: 05/22/03 

Date: Thu, 22 May 2003 14:03:50 -0600

This is my attempt to come up with a complete list of process attributes.
The notation "(thread)" means that the attribute is really an attribute of a
thread, not of the whole process.

The following attributes are not on the list because they are not attributes
of a process:

     memory, shared segment IDs (SysV)
     memory, shared segments (POSIX)
     memory, shared segments (SysV)
     message queue IDs (SysV)
     message queues (POSIX)
     message queues (SysV)
     semaphore set IDs (SysV)
     semaphore sets (SysV)
     semaphores, named (POSIX)

The question is: Can you spot any omissions or other mistakes?

Thanks!

--Marc

-------------------------
asynchronous I/O operations
atexit-registered functions
controlling terminal
conversion descriptors
directory stream positioning
directory streams
directory, current
directory, root
exit status
file descriptions
file descriptors
file locks
file-mode creation mask
floating-point environment (fegetenv)
ID, effective group
ID, effective user
ID, parent process
ID, process
ID, process-group
ID, real group
ID, real user
ID, saved set-group-ID
ID, saved set-user-ID
ID, thread (thread)
IDs, supplementary group
limit, resources (incl. file size)
memory, data segment
memory, data segment, arguments
memory, data segment, environment
memory, instruction segment
memory, locks (mlock)
memory, mappings (POSIX and SysV)
memory, stack (thread)
message catalog descriptors
message-queue descriptions (POSIX)
message-queue descriptors (POSIX)
pipes (FIFO)*
pipes (unnamed)
scheduling, nice value
scheduling, SCHED_FIFO and SCHED_RR policies
semaphores, memory (POSIX)
semaphores, semadj values (SysV)
session membership
signal actions
signal alternate stack
signal mask (thread)
signals pending
sockets
thread barriers (thread)
thread condition variables (thread)
thread mutexes (thread)
thread read-write locks (thread)
thread spin lock (thread)
threads (thread)
thread-specific data (thread)
time, CPU
time, CPU-time clock (CPT)
time, CPU-time clock of the thread
timer, alarm
timers, interval
timers, per-process
tracing attributes

---------------

*FIFO itself has same persistence as other files, but data in it goes away
if no process has it opened for reading

Relevant Pages

  • Re: very high memory usage in -current
    ... Maybe it's related to jemalloc, but I'd be surprised if no one else has noticed this before. ... The application would allocate some large chunks of memory for image ... These data would be allocated in the data segment. ...
    (freebsd-current)
  • Re: Static constructors/destructors
    ... Object instances go to the data segment and anything in data segment must be freed as soon as process frees an object pointer. ... If a static field is subject to change, I am not sure, but the pointer to it should be in text segment and the memory should be allocated on stack/heap depending on it's type, even in that case the pointer can not be dereferenced and so, the memory used by static fields will never be deleted in process lifetime. ... it doesn't quite make sense to match a static constructor with a single destructor. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Kind of new: function implementation questions, MASM
    ... In 32-bit programming, you should simply ignore these concepts. ... A stack is just a piece of memory. ... >indicate it's a register definition. ... >the data segment to be a block of memory that I can access. ...
    (comp.lang.asm.x86)
  • Re: Complete list of process attributes?
    ... file write positioning ... stream write positioning ... memory stack ... memory, shared segment IDs (SysV) ...
    (comp.unix.programmer)
  • Re: CreateThread Fails with ERROR_NOT_ENOUGH_MEMORY....
    ... We were able to figure out the stack of the culprit func. ... We have dispatched the bug to the relevant group owning the routine which was leaking semaphores & events & they are looking into it now. ... As far as the VM usage is concerned, I still believe that, given the amount of stress involved in the test, we are bound to run out of virtual memory. ... Now about the memory leak. ...
    (microsoft.public.win32.programmer.kernel)