| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Mainly focus on files that use BSD 2-Clause license, however the tool I
was using mis-identified 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.
|
|
|
|
|
| |
Reviewed by: des, emaste
Differential Revision: https://reviews.freebsd.org/D11690
|
|
|
|
|
| |
Reported by: koobs@, araujo@, linimon@, bjk@, emaste@, jhb@, ngie@, cem@
Maintainer timeout: des@
|
|
|
|
|
| |
an example of how not to make it more portable. I've had this lying
around uncommitted since 2009...
|
|
|
|
|
|
|
| |
for the SGI Altix 350 to FreeBSD/ia64. The hardware used for porting
is a two-module system, consisting of a base compute module and a
CPU expansion module. SGI's NUMAFlex architecture can be an excellent
platform to test CPU affinity and NUMA-aware features in FreeBSD.
|
|
|
|
|
|
| |
The problem with fcntl(2) locks is that they are not inherited by child
processes. This breaks pidfile(3), where the common idiom is to open
and lock the PID file before daemonizing.
|
|
|
|
| |
lock if the file is opened with O_RDONLY.
|
| |
|
|
|
|
| |
Approved by: re (kensmith)
|
|
|
|
| |
Approved by: re (kensmith)
|
| |
|
| |
|
|
|
|
|
|
| |
locked it.
MFC after: 3 weeks
|
|
|
|
| |
that I make stupid fundamental mistakes like this when I don't.
|
| |
|
|
|
|
| |
MFC after: 3 weeks
|
|
flopen(3) function which reliably opens and locks a file.
MFC after: 3 weeks
|