Don't call setgrent() in an unportable way.
ClosedPublic
Actions

Authored by ed on May 31 2016, 1:44 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Apr 27 2024, 6:21 PM

	Unknown Object (File)
	Apr 27 2024, 6:04 PM

	Unknown Object (File)
	Dec 22 2023, 9:12 PM

	Unknown Object (File)
	Dec 14 2023, 1:35 AM

	Unknown Object (File)
	Nov 14 2023, 4:51 AM

	Unknown Object (File)
	Oct 26 2023, 4:47 AM

	Unknown Object (File)
	Sep 25 2023, 6:23 AM

	Unknown Object (File)
	Aug 10 2023, 6:37 PM

View All 34 Files

Subscribers

imp

Details

Reviewers

oshogbo

Commits

rS301167: Don't call setgrent() in an unportable way.

Summary

For FreeBSD 12, I'm considering updating setgrent() to have a function
prototype that conforms to POSIX. FreeBSD seems to be the only operating
system that lets setgrent() return an integer. It's also inconsistent
with setpwent().

It looks like our libcasper depends on setgrent() returning an integer.
Get rid of that.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

ed updated this revision to Diff 17149.May 31 2016, 1:44 PM

ed retitled this revision from to Don't call setgrent() in an unportable way..

ed updated this object.

ed edited the test plan for this revision. (Show Details)

ed added a reviewer: oshogbo.

Herald added a subscriber: imp. · View Herald TranscriptMay 31 2016, 1:44 PM

Looks good for me.

This revision is now accepted and ready to land.Jun 1 2016, 7:55 PM

Closed by commit rS301167: Don't call setgrent() in an unportable way. (authored by ed). · Explain WhyJun 1 2016, 8:45 PM

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

Path

Size

head/

lib/

libcasper/

services/

cap_grp/

cap_grp.c

4 lines

Diff 17199

View Options

head/lib/libcasper/services/cap_grp/cap_grp.c

Don't call setgrent() in an unportable way.ClosedPublicActions