summaryrefslogtreecommitdiffstats
path: root/lib/libc
Commit message (Collapse)AuthorAgeFilesLines
* Docuemnt exactly which functions access which NSS databases.bms2007-01-221-1/+15
| | | | | | | | Point out that FreeBSD libc has compat stubs for GNU glibc NSS modules which access NSDB_PASSWD/NSDB_GROUP, but not NSDB_HOSTS; based on painful experience porting nss_mdns. Reviewed by: ru
* o Remove duplicate includes.maxim2007-01-203-3/+0
| | | | Obtained from: Slava Semushin via NetBSD
* On FreeBSD/arm, any value > 50 bits will result in a rediculously hugeimp2007-01-191-2/+2
| | | | | | | | | | | number being returned for mktime and timegm calls. Choose 48 because that works well. This does reduce the dynamic range of tm_year from about 2 billion years down to "only" about 9 million years. Please contact me if this restriction poses a problem. Due to the complexity of the code, I admit that I didn't trace down what, exactly, was overflowing with longer bits. This fixes software that we run on the embedded systems we have.
* When we try to set set-gid bit with chmod(2) on a file, which we own, but ourpjd2007-01-161-1/+5
| | | | | | effective group ID (and any of our group) doesn't match the group ID of the file, we get EPERM. This doesn't conform POSIX. POSIX requires that we should return 0, but silently clear the set-gid bit.
* Remove 3rd clause, renumber, ok per emailimp2007-01-125-20/+5
|
* o Document SO_TIMESTAMP and SO_BINSTAMP socket options.maxim2007-01-111-2/+46
| | | | | | | | PR: docs/107696 Submitted by: Rob Robertson Reviewed by: ru Obtained from: NetBSD (mostly) MFC after: 1 week
* Remove silly n that crept inimp2007-01-091-1/+1
|
* Per Regents of the University of Calfornia letter, remove advertisingimp2007-01-09749-3005/+1
| | | | | | clause. # If I've done so improperly on a file, please let me know.
* Be more specific in ENXIO description:pjd2007-01-071-3/+4
| | | | | | - O_NONBLOCK flag has to be set, if it is not set, open(2) will wait for another process opening the fifo for reading, - Use O_WRONLY which implies that the file has to be opened _only_ for write.
* open(2) returns EROFS when O_CREAT is specified and the named file wouldpjd2007-01-071-0/+3
| | | | reside on a read-only file system.
* - POSIX mentions that EACCES can be returned when O_TRUNC is specifiedpjd2007-01-071-1/+18
| | | | | separately. Do the same. - Document when EPERM can be returned.
* Prefer "to be modified" over "to be opened for writing".pjd2007-01-071-1/+1
| | | | | | | | | | This is quite tricky situation, because we allow to open a file with O_RDONLY|O_TRUNC. O_TRUNC modifies a file, but we actually don't open it for writing. EISDIR is also returned when we try to open a directory O_RDONLY|O_TRUNC, which is correct. POSIX says that "The result of using O_TRUNC with O_RDONLY is undefined.", we choose to accept it (Solaris did the same), that's why "to be modified" seems more accurate to me.
* Handle inf/nan correctly.das2007-01-061-2/+14
|
* The distinction between quiet and signaling NaN formats isdas2007-01-036-0/+128
| | | | | machine-dependent; these files tell the latest version of gdtoa what to do.
* Fix rounding of 0xf for hex fp formats.das2007-01-032-3/+3
| | | | PR: 90333
* Bump modification date for last update.simon2006-12-281-1/+1
|
* Catch up struct cmsghdr and struct msghdr in the manual page with thesimon2006-12-281-11/+11
| | | | | | actual structures in socket.h (which were updated 7 years ago). MFC after: 1 week
* Fix a typo in __fpu_ftox() that caused long double to long (and long long)marius2006-12-241-9/+10
| | | | | | | | | conversion of negative numbers to always result in -1. While at it, rearrange the nearby comment so it fits in 80 chars per line, like the rest of this file does. PR: 107130 MFC after: 1 day
* Implement chunk allocation/deallocation hysteresis by caching one sparejasone2006-12-231-51/+86
| | | | | | | | chunk per arena, rather than immediately deallocating all unused chunks. This fixes a potential performance issue when allocating/deallocating an object of size (4kB..1MB] in a loop. Reported by: davidxu
* add a missing the...jmg2006-12-191-1/+1
| | | | MFC after: 3 days
* Consistently use a socklen_t type where required, and eliminaterodrigc2006-12-161-6/+6
| | | | | | | GCC warning "dereferencing type-punned pointer will break strict-aliasing rules". Reviewed by: rrs
* Merge BIND9 9.3.3 into main chunk.ume2006-12-155-20/+17
| | | | | Obtained from: ISC MFC after: 1 week
* This commit was generated by cvs2svn to compensate for changes in r165254,ume2006-12-151-5/+5
|\ | | | | | | which included commits to RCS files with non-trunk default branches.
| * Vendor import of BIND 9.3.3ume2006-12-156-25/+22
| |
| * Import of BIND 9.3.3rc2ume2006-10-241-7/+7
| |
* | chflags(2) returns EPERM when user tries to set or remove the SF_SNAPSHOT flag.pjd2006-12-151-0/+4
| |
* | This adds the "system calls"rrs2006-12-152-1/+830
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | sctp_getaddrlen() sctp_connectx() sctp_bindx() sctp_opt_info() sctp_getpaddrs() sctp_freepaddrs() sctp_getladdrs() sctp_freeladdrs() sctp_sendmsg() sctp_getassocid() sctp_send() sctp_sendx() sctp_sendmsgx() sctp_recvmsg() sctp_peeloff() Manual pages will be forthcoming (and the commit to porters-handbook)
* | band-aide until _SC_PHYS_PAGES actually is definedimp2006-12-141-0/+2
| |
* | Add support for _SC_PHYS_PAGES, which is not standard, but can be found inpjd2006-12-142-1/+27
| | | | | | | | Solaris and Linux.
* | Document _SC_PAGESIZE. There are still 85 undocumented variables.pjd2006-12-141-1/+3
| | | | | | | | Obtained from: NetBSD
* | - truncate(2) returns EFBIG if the length argument was greater than thepjd2006-12-131-1/+9
| | | | | | | | | | maximum file size. - truncate(2) returns EINVAL if the length argument was less than 0.
* | Append-only flag also denies chown(2).pjd2006-12-131-1/+1
| |
* | Much more correct EFTYPE description.pjd2006-12-131-1/+3
| |
* | Better wording.pjd2006-12-132-2/+2
| |
* | Append-only flag also denies chmod(2). Is this correct behaviour?pjd2006-12-131-1/+1
| |
* | Be more precise with EPERM description. When chown(2) is a no-op, it willpjd2006-12-131-1/+2
| | | | | | | | return 0.
* | Write permission if of course only needed for the parent directory ofpjd2006-12-132-8/+4
| | | | | | | | | | | | the object beeing created. Pointed out by: bde
* | mkfifo(2) returns EACCES when write permission is denied for a component ofpjd2006-12-131-0/+2
| | | | | | | | the path prefix.
* | Be more specific when ELOOP can be returned.pjd2006-12-121-1/+3
| |
* | symlink(2) return EACCES if a component of the name2 path prefix deniespjd2006-12-121-0/+4
| | | | | | | | write permission.
* | Correct ENOENT description.pjd2006-12-121-2/+4
| |
* | The 'name1' argument to symlink(2) is only limited to 1023 characters,pjd2006-12-121-1/+3
| | | | | | | | its components are not checked.
* | mkdir(2) creates directory, not file.pjd2006-12-121-1/+2
| |
* | Remove reference to confusing behaviour just removed fromjulian2006-12-121-6/+3
| | | | | | | | the kse_exit() syscall. Describe the correct behaviour.
* | When directory is given as an argument for unlink(2), EPERM is returnedpjd2006-12-101-4/+1
| | | | | | | | not matter if this is regular directory or a mount point.
* | If the named file has its immutable or append-only flag set, utimes(2)pjd2006-12-091-1/+6
| | | | | | | | returns EPERM.
* | If the parent directory of the named file has its immutable flag set,pjd2006-12-091-1/+6
| | | | | | | | mkfifo(2) returns EPERM.
* | If the parent directory of the destination file has its immutable flag set,pjd2006-12-091-1/+8
| | | | | | | | symlink(2) returns EPERM.
* | - If the source file has its immutable or append-only flag set, link(2)pjd2006-12-091-4/+13
| | | | | | | | | | | | returns EPERM. - If the parent directory of the destination file has its immutable flag set, link(2) returns EPERM.
* | If the named file has its immutable or append-only flag set, truncate(2)pjd2006-12-091-1/+6
| | | | | | | | | | | | | | and ftruncate(2) return EPERM. Note, that if the append-only flag is set even increasing size of the file is not permitted.
OpenPOWER on IntegriCloud