| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
There is no reason why these three variables should be declared as
global variables, while the others aren't. They are only used inside
main().
|
|
|
|
|
| |
Most of these tools build with WARNS=6, except for their use of K&R
function declarations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
system callers of getgroups(), getgrouplist(), and setgroups() to
allocate buffers dynamically. Specifically, allocate a buffer of size
sysconf(_SC_NGROUPS_MAX)+1 (+2 in a few cases to allow for overflow).
This (or similar gymnastics) is required for the code to actually follow
the POSIX.1-2008 specification where {NGROUPS_MAX} may differ at runtime
and where getgroups may return {NGROUPS_MAX}+1 results on systems like
FreeBSD which include the primary group.
In id(1), don't pointlessly add the primary group to the list of all
groups, it is always the first result from getgroups(). In principle
the old code was more portable, but this was only done in one of the two
places where getgroups() was called to the overall effect was pointless.
Document the actual POSIX requirements in the getgroups(2) and
setgroups(2) manpages. We do not yet support a dynamic NGROUPS, but we
may in the future.
MFC after: 2 weeks
|
|
|
|
| |
from Berkeley.
|
|
|
|
|
|
|
| |
when chrooting.
Obtained from: NetBSD
MFC after: 4 weeks
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Submitted by: Maxime Henrion <mux@qualys.com>
MFC after: 2 weeks
|
|
|
|
| |
Idea from: Theo de Raadt <deraadt@openbsd.org>
|
| |
|
| |
|
|
|
|
| |
posix standard on the topic.
|
|
|