| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
TAI is a timescale, just like UTC. The tai field returns the offset
between the two, and isn't really used for precision time keeping.
Explain in brief what a positive and a negative leap seconds are. Add
some URLs to very useful web pages about time and time keeping for
more information on using this API.
Reviewed by: phk
|
|
|
|
|
|
| |
Use the latter for gdtoa.
Requested by: deischen (far too long ago)
|
|
|
|
| |
Noticed by: kris
|
|
|
|
| |
Reviewed by: imp
|
| |
|
|
|
|
|
|
|
| |
or -1 on failure. The manual used to say it returned 0 or -1. Both
examination of the kernel sources, and ntpd show that this is the case.
MFC After: 3 days
|
| |
|
|
|
|
|
|
|
| |
that has been here for 6 years and 9 months.
Reviewed by: deischen
MFC After: 1 week
|
|
|
|
|
|
|
|
|
| |
Also fixed the rest of ell (list) functions prototypes to include
a (commented out) terminating null pointer.
Pointed out by: bde
Obtained from: POSIX.1-2001
Glanced at by: imp
|
| |
|
|
|
|
| |
Confused: anordby
|
| |
|
|
|
|
|
|
|
|
|
| |
replaced just fine with getpeereid() and the whole code
gets a lot simpler. We don't break the ABI, since all server
programms use __rpc_get_local_uid(), and we just change library
internals.
Reviewed by: des
|
| |
|
|
|
|
|
| |
PR: 52612
Submitted by: Marc Olzheim <marcolz@ilse.nl>
|
|
|
|
|
|
| |
It is only possible to do this on an ABI that has a compulsory frame
pointer, which the amd64 ABI does not. Thus, it is only possible to
implement this as a compiler builtin.
|
|
|
|
|
|
|
| |
fgetrune(), fputrune(), fungetrune(), mbrune(), mbrrune(), mbmb(),
setinvalidrune(), UTF2 encoding method.
These have been marked as being deprecated in their manual pages since 5.0,
and their use causes a linker warning.
|
|
|
|
|
|
|
| |
memory leaks (fixes bugs earlier purported to be fixed).
Submitted by: Ed Moy <emoy@apple.com>
Obtained from: Apple Computer, Inc.
MFC after: 2 weeks
|
|
|
|
|
| |
(untested, but existing state breaks
http://triangle.rtp.freebsd.org/~des/tinderbox-CURRENT-amd64-amd64.brief)
|
| |
|
|
|
|
|
|
|
| |
code is always compiled into the kernel now.
Submitted by: Hubert Tournier <hubert@frbsd.org>
PR: docs/53068
|
| |
|
| |
|
| |
|
|
|
|
| |
instead of .Xr when needed
|
|
|
|
| |
Format other unknown devices consistently in hex.
|
|
|
|
|
|
|
|
|
| |
that the old API (passing "" as the attribute name to the _get_
interface) is now deprecated (and was probably a bad idea).
Pointed out by: Dominic Giampaolo <dbg@apple.com>
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
|
|
|
| |
Approved by: des (mentor)
|
| |
|
|
|
|
| |
to a random memory location. Perl works a lot better with this.
|
| |
|
|
|
|
|
|
| |
o Make sure the arguments to ctx_wrapper() are loaded from the
backing store by forcing an underflow. Do this by making all
registers in the register frame local.
|
|
|
|
| |
Submitted by: bde
|
| |
|
|
|
|
|
| |
PR: 51504
Submitted by: Statue <statue@freebsd.sinica.edu.tw>
|
|
|
|
| |
Submitted by: Nadav Eiron <nadav@TheEirons.org>
|
|
|
|
| |
function pointer passed in.
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Up to 8 arguments are allowed. This is the number of arguments
passed in registers. Subsequent registers are passed on the stack.
Trying to deal with this is not easy in C and likely forces us to
use assembly code. Let's avoid that for now. There's no indication
that more than 8 arguments is a strong requirement (Linux also has
an 8 argument limit).
o We expect that the stack base is 16-byte aligned and the stack
size is a multiple of 16-byte. We bomb out if this is not the case.
We probably want to be less strict by enforcing it ourselves. For
now it's better to not hide gross alignment bogons by silently
correcting it.
|
|
|
|
|
|
|
|
|
|
| |
to a buffer in the big key/data case, memmove() was used on pointers
to size_ts, but only sizeof(u_int32_t) bytes where copied. This broke
on big_endian architectures where sizeof(size_t) > sizeof(u_int32_t).
This bug broke portupgrade (by way of ruby_bdb1) on sparc64.
Approved by: re (rwatson)
|
|
|
|
|
|
| |
my last commit.
Approved by: re (scottl)
|
|
|
|
|
|
|
|
| |
some strange reason recvmsg() never sets errno to EAGAIN
on a non-blocking socket and just returns 0.
Reviewed by: jhb
Approved by: re
|
|
|
|
|
|
|
|
|
| |
are not initialized at this place. Move the initializing
before the non-blocking check.
Submitted by: Marius Strobl <marius@alchemy.franken.de>
Reviewed by: jhb
Approved by: re
|
|
|
|
|
|
|
|
|
| |
just read() in non-blocking mode too. The reason is obvious. NetBSD
uses a complete different way to get the credentials so this patch
only applies to FreeBSD.
Reviewed by: rwatson
Approved by: re
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the special treatment of non-blocking mode in
the "look ahead function" xdrrec_eof(). It currently
assumes that the last read() in a row of several reads
does not have zero lenght. If this is the case, svc_vc_stat()
does return XPRT_MOREREQS, and the RPC-request aborts because
there is no data to read anymore.
To fix this, go back to the original version of the code
for non-blocking mode until NetBSD comes up with another
possible fix like this one in xdrrec_eof()
if (rstrm->last_frag && rstrm->in_finger == rstrm->in_boundry) {
return TRUE;
}
Return always FALSE in set_input_fragment() for non-blocking
mode. Since this was not used in FreeBSD, I omitted it at the
first time. Now we use this function and we should always
return FALSE for it.
Reviewed by: rwatson
Approved by: re
|
|
|
|
|
| |
PR: 52686
MFC after: 1 day
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
| |
implications of native PC relative addressing.
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
| |
Approved by: re (blanket)
|