Revision tags: release/14.0.0 |
|
#
b3e76948 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: two-line .h pattern
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
|
#
4d846d26 |
| 10-May-2023 |
Warner Losh <imp@FreeBSD.org> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg MFC After: 3 days Sponsored by: Netflix
show more ...
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0 |
|
#
1de7b4b8 |
| 27-Nov-2017 |
Pedro F. Giffuni <pfg@FreeBSD.org> |
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
No functional change intended.
show more ...
|
Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0 |
|
#
10b3b545 |
| 17-Sep-2009 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Merge from head
|
#
2e370a5c |
| 26-May-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
Merge from HEAD
|
#
096d622d |
| 26-May-2009 |
Brian Somers <brian@FreeBSD.org> |
Fix a race that can stall the timer when we remove a timer that has another timer with a <0.05 second delta next to it.
This is done by avoiding the possibility of updating the first residual time d
Fix a race that can stall the timer when we remove a timer that has another timer with a <0.05 second delta next to it.
This is done by avoiding the possibility of updating the first residual time delta in the timer list to zero.
PR: 102747 Submitted by: Sergey Zaharchenko - doublef-ctm at yandex dot ru MFC after: 3 weeks
show more ...
|
Revision tags: release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0, release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs |
|
#
6eafd353 |
| 27-Aug-2002 |
Brian Somers <brian@FreeBSD.org> |
Include the correct file (stdarg.h) and use va_list rather than _BSD_VA_LIST_
Suggested by: mike
|
Revision tags: release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs |
|
#
10be78d3 |
| 15-Jun-2002 |
Brian Somers <brian@FreeBSD.org> |
Remove whitespace at the end of lines.
|
#
b08bf2de |
| 22-May-2002 |
Brian Somers <brian@FreeBSD.org> |
Add some missing #includes that weren't required due to namespace polution in our headers.
Submitted by: bde
|
#
6f4cd656 |
| 14-May-2002 |
Brian Somers <brian@FreeBSD.org> |
Fix an include for NetBSD
|
#
de59e178 |
| 14-May-2002 |
Brian Somers <brian@FreeBSD.org> |
o Clean up some #includes o Bump version number to 3.0.4 o When talking to a RADIUS server, provide a NAS-Port-Type.
When the NAS-Port-Type is Ethernet, provide a NAS-Port value equal to the SES
o Clean up some #includes o Bump version number to 3.0.4 o When talking to a RADIUS server, provide a NAS-Port-Type.
When the NAS-Port-Type is Ethernet, provide a NAS-Port value equal to the SESSIONID from the environment in direct mode or the NGM_PPPOE_SESSIONID message in other modes. If no SESSIONID is found, default to the interface index in client mode or zero in server mode.
When the NAS-Port-Type is ISDN, set the NAS-Port to the minor number of the physical device (ie, the N in /dev/i4brbchN).
This makes it easier for the RADIUS server to identify the client WRT accounting data etc.
Prompted by: lsz8425 <lsz8425@mail.cd.hn.cn>
show more ...
|
Revision tags: release/4.5.0_cvs, release/4.4.0_cvs |
|
#
ed1e8460 |
| 13-Sep-2001 |
Brian Somers <brian@FreeBSD.org> |
sigpause() -> sigsuspend() sigblock() -> sigprocmask()
|
#
65309e5c |
| 13-Jun-2001 |
Brian Somers <brian@FreeBSD.org> |
Convert IIJ copyrights to BSD copyrights.
Approved by: Toshiharu OHNO <tohno@sirius.ocn.ne.jp>
|
Revision tags: release/4.3.0_cvs, release/4.3.0, release/4.2.0, release/4.1.1_cvs, release/4.1.0, release/3.5.0_cvs, release/4.0.0_cvs |
|
#
76ce2d4b |
| 14-Mar-2000 |
Brian Somers <brian@FreeBSD.org> |
When adjusting timer::rest, round to the closest TICKUNIT usecs value.
This has minimal impact here, but if ppp ever needs to frequently remove timers before they've timed out, it can badly skew the
When adjusting timer::rest, round to the closest TICKUNIT usecs value.
This has minimal impact here, but if ppp ever needs to frequently remove timers before they've timed out, it can badly skew the next item in the timer list without this change.
The correct fix would be to store usecs in `rest' rather than TICKUNITs, but the math is easier if we just round...
show more ...
|
#
e722aa17 |
| 14-Mar-2000 |
Brian Somers <brian@FreeBSD.org> |
When we stop a timer that's the first in the timer list, ensure that we adjust that timers `rest' value (with the current getitimer() values) before using that to adjust the next items `rest' value.
When we stop a timer that's the first in the timer list, ensure that we adjust that timers `rest' value (with the current getitimer() values) before using that to adjust the next items `rest' value. After adjusting that value, restart the timer service so that we've now got the correct setitimer() values.
show more ...
|
#
182c898a |
| 27-Dec-1999 |
Brian Somers <brian@FreeBSD.org> |
Add a bunch of `const's and fix a typo.
Submitted by: Rich Neswold <rneswold@MCS.Net>
|
Revision tags: release/3.4.0_cvs |
|
#
83569b35 |
| 20-Nov-1999 |
Brian Somers <brian@FreeBSD.org> |
Update the time delta of the first item in TimerList before inserting a new item. Without this, it's possible to mis-insert quite badly... but only by as much as the load of the first item, which is
Update the time delta of the first item in TimerList before inserting a new item. Without this, it's possible to mis-insert quite badly... but only by as much as the load of the first item, which is almost always 1 second.
Initialise the timerservice with `restart' set if we're inserting at the start of the list.
show more ...
|
#
c2e1f0e3 |
| 15-Oct-1999 |
Brian Somers <brian@FreeBSD.org> |
When more than one timer is expired at once, allow for the possibility that the first timer ends up doing a timer_Stop() on the second.
When this happens, remove the timer from the pending list so t
When more than one timer is expired at once, allow for the possibility that the first timer ends up doing a timer_Stop() on the second.
When this happens, remove the timer from the pending list so that we still call any subsequent timers.
This bug has been here for several years, but has only been tickled recently with my device layering changes.
With enormous thanks for the perseverance of: Ruslan Ermilov <ru@ucb.crimea.ua>
show more ...
|
Revision tags: release/3.3.0_cvs |
|
#
97d92980 |
| 28-Aug-1999 |
Peter Wemm <peter@FreeBSD.org> |
$Id$ -> $FreeBSD$
|
Revision tags: release/3.2.0 |
|
#
d543a9c0 |
| 12-May-1999 |
Brian Somers <brian@FreeBSD.org> |
Adjust our first timer delta according to the return from getitimer() so that times are correct for ``show timer''.
|
#
3377c28c |
| 09-May-1999 |
Brian Somers <brian@FreeBSD.org> |
Deal with the fact that as we now mbuf_Read the fsm header in fsm_Input() we often end up with a NULL mbuf.
Deal with a possible NULL mbuf being passed into mbuf_Prepend().
Adjust some spacing to m
Deal with the fact that as we now mbuf_Read the fsm header in fsm_Input() we often end up with a NULL mbuf.
Deal with a possible NULL mbuf being passed into mbuf_Prepend().
Adjust some spacing to make things more consistent.
show more ...
|
Revision tags: release/3.1.0, release/3.0.0, release/2.2.8 |
|
#
7e778f13 |
| 14-Dec-1998 |
Brian Somers <brian@FreeBSD.org> |
Rather than interrupting 10 times per second then checking to see if there's anything to do, schedule the next alarm based on the next required timeout. This decreases the load when there are lots of
Rather than interrupting 10 times per second then checking to see if there's anything to do, schedule the next alarm based on the next required timeout. This decreases the load when there are lots of relatively idle ppp processes.
While I'm in there, handle the possibility that a timeout makes the timer element go out of scope by grabbing the enext pointer before executing the timer function.
show more ...
|
Revision tags: release/2.2.7 |
|
#
10a9be1e |
| 27-Jun-1998 |
Brian Somers <brian@FreeBSD.org> |
Remove redundant includes
|
#
d2a69fc3 |
| 20-Jun-1998 |
Brian Somers <brian@FreeBSD.org> |
Re-initialise our timer service after fork()ing to lose our terminal session. Is this a bug in setitimer() ? - it must be called again in the child !
|
#
d93d3a9c |
| 15-Jun-1998 |
Brian Somers <brian@FreeBSD.org> |
o De-staticise things that don't need to be static. o Bring the static ``ttystate'' into struct prompt so that the tilde context is per prompt and not global. o Comment the remaining static variabl
o De-staticise things that don't need to be static. o Bring the static ``ttystate'' into struct prompt so that the tilde context is per prompt and not global. o Comment the remaining static variables so that it's clear why they're static. o Add some XXX comments suggesting that our interface list and our hostname should be re-generated after a signal (say SIGUSR1) so that a machine with PCCARDs has a chance.
show more ...
|