If the OS kernel imposes no limit whatsoever, and the limit
is thusly whatever memory is available, how do you define PATH_MAX?
POSIX requires that for this case, PATH_MAX is not defined as a
constant in <limits.h>, and [f]pathconf(..., _PC_PATH_MAX) returns -1
without changing errno.
Geoff Clare <netnews@xxxxxxxxxxxxx>
- Re: close fd while select/poll/epoll
... out of memory other than malloc returning NULL. ... POSIX *cannot* make this illegal. ... my proposal becomes part of the standard. ...
- Re: posix and lock-free algorithms
... than one thread of control is restricted such that no thread of control can read or modify a memory location while another thread of control may be modifying it." ... It's a pretty stupid claim that the compiler might optimize across an external call when those external routines may contain calls to "memory synchronizing" Posix functions. ...
- Re: data protected not by mutexes but program logic
... ensures cache coherence for all the memory. ... Y is write-protected by a mutex but read-protected by a semaphore. ... but looking at POSIX I don't see SysV semaphores doing that. ... So I'd like to get rid of that lock. ...
- Re: does fsync() imply msync()?
... this isn't required behavior by posix, that is, that fsync ... The posix language reads "all data for the open file descriptor named by ... memory ranges mmap'd from a file ... descriptor after it was used to establish a memory mapping and to ...
- Re: (POSIX?) Machine independent data passing?
... I was hoping someone here could jog my memory - If I recall correctly ... there is a (possibly POSIX?) set of fairly standard functions that were ...