summaryrefslogtreecommitdiffstats
path: root/lib/libc
Commit message (Collapse)AuthorAgeFilesLines
...
* Remove single-space hard sentence breaks. These degrade the qualitysheldonh2000-03-0247-147/+294
| | | | | of the typeset output, tend to make diffs harder to read and provide bad examples for new-comers to mdoc.
* Fix errors in .Xr usage.nik2000-03-011-1/+1
| | | | | PR: docs/17057 Submitted by: Submitted by: Udo Erdelhoff <ue@nathan.ruhr.de>
* Add MAP_NOCORE to mmap(2), and MADV_NOCORE and MADV_CORE to madvise(2).ps2000-02-282-0/+8
| | | | | | | | | | | | This This feature allows you to specify if mmap'd data is included in an application's corefile. Change the type of eflags in struct vm_map_entry from u_char to vm_eflags_t (an unsigned int). Reviewed by: dillon,jdp,alfred Approved by: jkh
* Restore `[no]{s|u}unlnk' and `[no]opaque' support.ru2000-02-223-6/+21
| | | | | | | Broken in src/bin/ls/stat_flags.c,v 1.12. PR: 16885 Approved by: jkh
* Change IPv6 scoped addr format again based on recent standard discussion.shin2000-02-192-9/+6
| | | | | | | | | Sorry for the flapping, but no change will be done for 4.0 anymore. Official standard will be published around April or later. If different format would be adopted at that time, then support for the new format will be added to the succeeding FreeBSD 4.x. Approved by: jkh
* Fix null-pointer dereference crash when the system is intentionallydillon2000-02-161-1/+2
| | | | | | | | | | | | | | | | run out of KVM through a mmap()/fork() bomb that allocates hundreds of thousands of vm_map_entry structures. Add panic to make null-pointer dereference crash a little more verbose. Add a new sysctl, vm.max_proc_mmap, which specifies the maximum number of mmap()'d spaces (discrete vm_map_entry's in the process). The value defaults to around 9000 for a 128MB machine. The test is scaled for the number of processes sharing a vmspace (aka linux threads). Setting the value to 0 disables the feature. PR: kern/16573 Approved by: jkh
* Add man pages for the sem_*() functions.jasone2000-02-166-0/+503
| | | | Approved by: jkh
* Fix coredump in gethostbyaddr() when the returned answer is too large tofenner2000-02-161-0/+4
| | | | | | | | | fit in the static buffer. This fix causes it to look like there is no data available, which is also wrong but is better than dumping core. PR: bin/10344 Reviewed by: billf Approved by: jkh
* Replace `.Os BSD' which caused a troff error with `.Bx' which alsochris2000-02-141-1/+1
| | | | happens to be the correct macro to use in this situation.
* Document the support in the kernel for hardware debug registers on theobrien2000-02-121-1/+20
| | | | | | ix86 platform which allows for hardware watchpoints, etc... Submitted by: Brian Dean <brdean@unx.sas.com>
* Add more dual stack consideration.shin2000-02-101-1/+5
| | | | | | | | -Should not error return when rresvport_af() failed for one of dest addrs resolved by getaddrinfo(). Should retry until all dest addr fail. Approved by: jkh
* Let getaddrinfo() and related functions supports traditional IPv4 formatshin2000-02-102-4/+10
| | | | | | | | | | | | | | | | | | | | | | | (shortend format, etc) Current KAME getaddrinfo() supports only d.d.d.d format IPv4 addr. But traditionally inet_aton() and etc support other formats. (shortend format and octal/deciaml/hex format) Aboud this, -As far as the discussion on freebsd-current, many people think traditional format should also be supported by getaddrinfo(). -X/Open spec requires getaddrinfo() also support those traditional IPv4 format. -RFC2553 say nothing about it. -As the result of confirmation in ietf/ipng list, there is no clear concensus yet, and the reply was, "RFC2553 update and X/Open spec will be in sync" So takeing these conditions into account, I think getaddrinfo() should also support traditional IPv4 format. Specified by: Marc Schneiders <marc@oldserver.demon.nl> Approved by: jkh
* Replace the existing documentation for ``KERN_QUANTUM'' with a morechris2000-02-101-4/+2
| | | | descriptive (and generally more useful) explanation.
* IPv6 scoped addr format is changed as recent KAME change.shin2000-02-092-6/+16
| | | | | | | | | | | | | | KAME scoped addr format is changed recently. before: addr@scope now: scope%addr Because the end of IPv6 numeric addr is tend to be truncated in `netstat -rn ` output, so placing scope part at starting of addr will be convenient. Approved by: jkh Obtained from: KAME project
* There is a problem in that one cannot use ctype.h at the same time as partsobrien2000-02-082-49/+145
| | | | | | | | | | | | | | of the C++ stdlib. Our ctype.h uses symbols of the form _<X> to denote the various character classes. Our ctype.h also extends the usual ctype.h offering by adding the "_T" (special) class. Problem is parts of the STL also use the symbol "_T" as its parameterized type. These two uses are incompatible. Thus change the form of the symbols used in ctype to something that fixes the current problem and is less likely to cause conflicts in the future. Requested by: Tomoaki NISHIYAMA <tomoaki@biol.s.u-tokyo.ac.jp> Ok'ed by: JKH
* Revert part of the last commit, remove {g|s}etflags from the libcjoe2000-02-051-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | | interface, and statically link them to the programs using them. These functions, upon reflection and discussion, are too generically named for a library interface with such specific functionality. Also the api that they use, whilst ok for private use, isn't good enough for a libc function. Additionally there were complications with the build/install-world process. It depends heavily upon xinstall, which got broken by the change in api, and caused bootstrap problems and general mayhem. There is work in progress to address future problems that may be caused by changes in install-chain tools, and better names for {g|s}etflags can be derived when some future program requires them. For now the code has been left in src/lib/libc/gen (it started off in src/bin/ls). It's important to provide library functions for manipulating file flag strings if we ever want this interface to be adopted outside of the source tree, but now isn't necessarily the right moment with 4.0-release just around the corner. Approved: jkh
* sync iruserok() extension API with other BSDsshin2000-02-011-28/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some of rcmd related function is need to be updated to support IPv6. Some of them are already updated as standard document. But there is also several de-facto functions and they are not listed in standard documents. They are, iruserok() (used by rlogind, rshd) ruserok() (used by kerberos, etc) KAME package updated those functions in original way. iruserok_af() ruserok_af() But recently there was discussion on IETF IPng mailing list about how to sync those API, and it is decided, -Those function is not standard and not documented. -But let BSDs sync their API as de-facto. And after some discussion, it is announced that -add update to iruserok() as iruserok_sa() -no ruserok() API change(it is only updated internaly) So I sync those API before 4.0 is released. The changes are, -prototype changes -ruserok() internal update (use iruserok_sa() inside) -removal of ruserok_af() -change iruserok_af() as static functioin, and also prefix the name with __. -add iruserok_sa() (Just call __iruserok_af() inside) -adding flag AI_ALL to getipnodebyaddr() called from __icheckhost(). This is necessary to support IPv4 communication via AF_INET6 socket could be correctly authenticated via iruserok_sa() -irusreok_af() call is replaced to iruserok_sa() call in rlogind, and rshd. Approved by: jkh
* Merge from RELENG_3 (oops):chris2000-01-291-5/+5
| | | | | resolved_name -> resolved_path resolvedname -> resolved_path
* Undo the ill-conceived breakage of the previous commit and really fix:jasone2000-01-293-26/+28
| | | | | | | | | | | | | | | | | | | | | | | | | For libc_r renamed syscalls, correct symbol naming from _thread_sys_foo() <-- _foo() to _thread_sys_foo() <-- _foo() <-- foo(). This is necessary for system calls which libc_r doesn't define foo(). Some weak symbols such as poll() are defined twice. From what I understand, depending on one weak symbol or the other to be used is a bad idea. All such weak symbols defined in the libc_r-specific code should therefore be made strong (non-weak?). Simplify PSEUDO() to not define any weak symbols, since they aren't ever needed. alpha/SYS.h: Correct reversed usage of WEAK_ALIAS(), which has reversed arguments from __weak_reference(). Also, fix reversal of symbols, so that syscall foo() is a weak alias for _foo(). Add WEAK_ALIAS() call to PRSYSCALL(), which unlike the i386 version of PRSYSCALL(), is not defined in terms of PSYSCALL(). Make PSEUDO() equivalent to the i386 version.
* Fix various typos and mdoc style issues.mpp2000-01-2911-54/+100
| | | | Reviewed by: rwatson
* Grammar fix: ``Different than'' should really be ``different from''.chris2000-01-291-1/+1
|
* Revive the warning that dllockinit() is experimental and subject tojdp2000-01-291-1/+6
| | | | change.
* For syscalls that are renamed to _thread_sys_foo, create a weak aliasjasone2000-01-283-16/+16
| | | | called _foo, not _thread_sys_foo.
* Introduce ACL man pages en masse for library calls, and general introduction.rwatson2000-01-2813-7/+1262
| | | | | | | Introduce ACL man pages en masse for library calls, and general introduction. Also, fix acl_valid.c non-portable calls to include _np in their names, making them standard-happy as well as consistent with acl.h
* There were so far only 42 different conversion specifications injoerg2000-01-282-0/+22
| | | | | | | | | strftime(3), add another one. :) %z yields the local timezone's offset in hours and minutes, as used in RFC822 headers. There's a precedence for this in Lunux' libc, and Internet software (like Perl scripts) start using it. OKed by (wrt. the code freeze): jkh
* Install setflags.3 and its link to getflags.3.bde2000-01-281-1/+3
|
* Simplify sytem call renaming. Instead of _foo() <-- _libc_foo <-- foo(),jasone2000-01-2770-274/+277
| | | | | | | | | | | | | | | | | just use _foo() <-- foo(). In the case of a libpthread that doesn't do call conversion (such as linuxthreads and our upcoming libpthread), this is adequate. In the case of libc_r, we still need three names, which are now _thread_sys_foo() <-- _foo() <-- foo(). Convert all internal libc usage of: aio_suspend(), close(), fsync(), msync(), nanosleep(), open(), fcntl(), read(), and write() to _foo() instead of foo(). Remove all internal libc usage of: creat(), pause(), sleep(), system(), tcdrain(), wait(), and waitpid(). Make thread cancellation fully POSIX-compliant. Suggested by: deischen
* Historically file flags (schg, uschg, etc) have been converted fromjoe2000-01-277-13/+247
| | | | | | | | | | | | | | | | | string to u_long and back using two functions, flags_to_string and string_to_flags, which co-existed with 'ls'. As time has progressed more and more other tools have used these private functions to manipulate the file flags. Recently I moved these functions from /usr/src/bin/ls to libutil, but after some discussion with bde it's been decided that they really ought to go in libc. There are two already existing libc functions for manipulating file modes: setmode and getmode. In keeping with these flags_to_string has been renamed getflags and string_to_flags to setflags. The manual page could probably be improved upon ;)
* o Back out rev 1.4 - reallocf() failure clobbers existing `environ'.ru2000-01-271-3/+8
| | | | | | | | o Do not override `environ' if realloc() fails, leave it intact. o Set `alloced' only when memory is actually allocated. PR: bin/5604 (2nd part) Reviewed by: bde
* Allow reverse lookup for loopback addr.shin2000-01-271-1/+1
| | | | | | This is merge from recent KAME fix to be more compliant with RFC2553. Obtained from: KAME project
* Fixed wrong includes in synopsis.bde2000-01-271-8/+11
| | | | | | | | | | | Updated date. 1987 was a while ago. Removed trailing comma in NAME section. Uncapitalised Bindresvport and Bindresvport_sa in DESCRIPTION section. Don't use .Nm there either. Added bindresvport_sa() to the RETURN VALUES and ERROR sections.
* Document the memory leak that is inherent in FreeBSD's semanticsarchie2000-01-261-0/+15
| | | | | | for getenv()/putenv(). PR: 10341 5604
* A few more touchups:rwatson2000-01-263-73/+94
| | | | | | | | | - clean up unneeded AFS ID type - Add Coda, NTFS, NWFS ACL types - Add acl_dup() prototype - Remove acl_calc_mask, which belongs in the editing library - Introduce posix1e.3, a man page introducing POSIX.1e library calls (more man pages to follow)
* Removed 3rd arg from bindresvport_sa() call, because the 3rd arg have beenshin2000-01-261-2/+1
| | | | | | already removed. Specified by: Philipp Mergenthaler <un1i@rz.uni-karlsruhe.de>
* bindresvport related changesshin2000-01-264-75/+138
| | | | | | | | | | -changed bindresvport2 to bindresvport_sa -merged the man into bindresvport.3 All discussion between Jean-Luc Richier <Jean-Luc.Richier@imag.fr>, Theo de Raadt <deraadt@cvs.openbsd.org>, itojun, is reflected to this code. (Actually Theo de Raadt write the code simultaneously as the discussion change.)
* Fix getaddrinfo() behaviour to be more compliant with RFC2553. Patches areshin2000-01-261-116/+17
| | | | | | | | | | | | obtained from itojun. -don't filter address families which are not supported by system at FQDN resolving. -don't do reverse lookup I think I checked all lib and tools which use getaddrinfo() if this change affect them. Obtained from: KAME project
* Minor fixes to library interface to improve POSIX.1e compliance. Thisrwatson2000-01-269-78/+65
| | | | | | | | | | adds _np to a couple of function prototypes that provided more broad/useful interfaces than POSIX.1e interfaces included. Also, move from using a heuristic to identify POSIX.1e-semantic ACLs to using different ACL types for non-POSIX.1e ACLs. This should clean up the existing fuzzy logic that determined when acl_sort() should be applied before kernel submission.
* several tcp apps IPv6 updateshin2000-01-253-5/+33
| | | | | | | | | | | | -inetd -rshd -rlogind -telnetd -rsh -rlogin Reviewed by: freebsd-arch, cvs-committers Obtained from: KAME project
* Improve the explanation on the (in)security of mktemp(3).sheldonh2000-01-251-3/+6
|
* We _do_ support MS_ASYNCguido2000-01-241-1/+1
| | | | Reviewed by: Matthew Dillon <dillon@apollo.backplane.com>
* Clarify that we don't offer hard realtime.alfred2000-01-241-3/+8
| | | | Split timeval options into 3 paragraphs, it's easier on my eyes.
* Remove unnecessary alternate entry points for *setjmp(). Make the mainjasone2000-01-209-48/+69
| | | | | | | entry point the standard name when not compiling libc_r (for example, longjmp is the main entry point instead of __longjmp). Suggested by: bde
* Move ENTRY and ALTENTRY definitions to asm.h where they belong.jasone2000-01-201-23/+0
| | | | | | Unbreak profiling. Again. Submitted by: bde
* Although it should be obvious that the 3-digit numeric values of thesheldonh2000-01-1912-12/+23
| | | | | characters shown are octal, state this explicitly for the easily misled.
* Make the quotes in the #include line visible.sheldonh2000-01-191-1/+1
|
* Make minor entry point changes to support libc_r.jasone2000-01-199-18/+18
|
* Fix bde'isms in acl/extattr syscall interface, renaming syscalls torwatson2000-01-196-14/+14
| | | | | | | | | prettier (?) names, adding some const's around here, et al. This is commit 4 out of 3, updating the userland library to reflect kernel interface changes. Reviewed by: bde
* Close PR#16028. Make the sanity check saner. The condition that wewpaul2000-01-191-1/+1
| | | | | | | | | check for on the server may arise legitimately on the client. The correct way to check for a zero record length is to check for it without the LAST_FRAG marker in it, since it's legal to send a LAST_FRAG marker with 0 bytes of data. PR: misc/16028
* Document KERN_QUANTUM under CTL_KERNchris2000-01-191-0/+6
| | | | | PR: 15637 Submitted by: jhs
* Document isnanf() for checking if a float is NaN (``Not-a-Number'') andchris2000-01-192-4/+9
| | | | | | create a link from isnanf.3 to isinf.3. PR: 13878
OpenPOWER on IntegriCloud