The Open Group. The Single UNIX Specification, Version 2 - 6 Vol Set for UNIX 98. Document number T912, The Open Group, February,  Home/Search   Document Not in Database   Summary   Related Articles   Check

....directory s GID. The purpose of this approach is to support project directories : users can save files into such specially set directories and the group owner automatically changes. However, setting the setgid bit on directories is not specified by standards such as the Single Unix Specification [Open Group 1997]. timestamps access and modification times are stored for each filesystem object. However, the owner is allowed to set these values arbitrarily (see touch(1) so be careful about trusting this information. All Unix like systems support this. The following are attributes are Linux unique ....

....for Linux and Unix HOWTO 3.2.4. Using Access Control Attributes 27 3.3. System V IPC Many Unix like systems, including Linux and System V systems, support System V interprocess communication (IPC) objects. Indeed System V IPC is required by the Open Group s Single UNIX Specification, Version 2 [Open Group 1997]. System V IPC objects can be one of three kinds: System V message queues, semaphore sets, and shared memory segments. Each such object has the following attributes: read and write permissions for each of creator, creator group, and others. creator UID and GID UID and GID of the creator ....

[Article contains additional citation context not shown here]

The Open Group. 1997. Single UNIX Specification, Version 2 (UNIX 98). http://www.opengroup.org/online-pubs?DOC=007908799.

....or may not be significant; we look forward to a careful analysis of IOCP performance scaling. Our contribution is not the concept of a pending event queue, but rather its application to UNIX, and our quantitative analysis of its scalability. 8. 2 Queued I O completion signals in POSIX The POSIX[16] API allows an application to request the delivery of a signal (software interrupt) when I O is possible for a given file descriptor. The POSIX Realtime Signals Extension allows an application to request that delivered signals be queued, and that the signal handler be invoked with a parameter ....

The Open Group, Woburn, MA. The Single UNIX Specification, Version 2 - 6 Vol Set for UNIX 98, 1997.

....paths between IP and each network adapter, for example. In general, the path abstraction often significantly affects the logic with which objects are created and destroyed, meaning that cleanly integrating such changes in a system not designed for paths is likely to be difficult. UNIX STREAMS [42] are superficially similar to Scout paths. A STREAM essentially consists of a sequence of modules that is terminated by a STREAM head at the top (beneath the user kernel boundary) and by a STREAM end at the bottom (device driver level) The sequence of modules in a STREAM is dictated by the ....

The Open Group. The Single UNIX Specification. Witney, England, second edition, February 1997. http://www.rdg.opengroup.org/pubs/catalog/t912.htm.

....but changes made to the underlying object that are not shadowed by a page in the shadow object are seen by the mapping process. This is the standard form of copy on write that most Unix like operating systems use, and it is the behavior specified for the mmap system call by the Unix standards [30]. ffl In a copy copy on write mapping the mapping process gets a complete snapshot of the object being mapped at the time of the mapping. The mapping process will not see changes other processes make to the unshadowed areas of the underlying object. This form of copy on write requires the use of ....

....pages directly and maps them into the buffer area. This prevents UVM from wasting map entries on the buffer area. 8. 10.2 Obsolete MAP FILE Interface The mmap system call supports two types of mappings: shared (MAP SHARED) and copyon write (MAP PRIVATE) These two types of mappings are standard [30]. Unfortunately, 4.4BSD also supports another mapping flag: MAP FILE. The MAP FILE constant is defined to be zero and the type of mapping it produces depends on what type of object is being mapped. If the object is a plain file, then the mapping is copy on write. However, if the object is a ....

The Open Group. The Single UNIX Specification, Version 2. The Open Group, 1998. See http://www.UNIX-systems.org/online.html.

....of IOCP performance scaling. Our contribution is not the concept of a pending event queue, but rather its application to UNIX, and our quantitative analysis of its scalability. A SCALABLE AND EXPLICIT EVENT DELIVERY MECHANISM FOR UNIX 14 8. 2 Queued I O completion signals in POSIX The POSIX[16] API allows an application to request the delivery of a signal (software interrupt) when I O is possible for a given file descriptor. The POSIX Realtime Signals Extension allows an application to request that delivered signals be queued, and that the signal handler be invoked with a parameter ....

The Open Group, Woburn, MA. The Single UNIX Specification, Version 2 - 6 Vol Set for UNIX 98, 1997.

No context found.

The Open Group. The Single UNIX Specification, Version 2 - 6 Vol Set for UNIX 98. Document number T912, The Open Group, February,

No context found.

The Open Group. The Single UNIX Specification, Version 2 - 6 Vol Set for UNIX 98. Document number T912, The Open Group, February, 1997.

No context found.

The Open Group. The Single UNIX Specification, Version 2 - 6 Vol Set for UNIX 98. Document number T912, The Open Group, February, 1997.

No context found.

The Open Group, The Single UNIX Specification, Version 2, http://www.opengroup.org/onlinepubs/7908799/xsh/mktime.html, 1997.

No context found.

The Open Group, ed.: The Single UNIX Specification, Version 3. The Open Group (2003) http://www.unix.org/version3/.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC