Fix handling of umtxp resource limit in sh(1), limits(1), and login.conf(5).
ClosedPublic
Actions

Authored by kib on Mar 11 2016, 7:41 PM.

Details

Reviewers

emaste
jilles

Group Reviewers

manpages

Commits

rS296723: Fix handling of umtxp resource limit in sh(1)/ulimit(1), limits(1), add

Summary

Title says it, make the umtxp resource limit settable from both sh/ulimit and from limits. I also updated the man pages, including reordering the pseudoterminals limits item, and updated summary/usage.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

kib updated this revision to Diff 14244.Mar 11 2016, 7:41 PM

kib retitled this revision from to Fix handling of umtxp resource limit in sh(1) and limits(1)..

kib updated this object.

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

kib added reviewers: jilles, emaste.

kib set the repository for this revision to rS FreeBSD src repository - subversion.

kib added a project: manpages.

Herald added a reviewer: manpages. · View Herald TranscriptMar 11 2016, 7:41 PM

Herald added a subscriber: imp. · View Herald Transcript

Handle login.conf(5).

Herald edited edge metadata. · View Herald TranscriptMar 11 2016, 8:49 PM

jilles requested changes to this revision.Mar 11 2016, 11:24 PM

jilles edited edge metadata.

jilles added inline comments.

lib/libutil/login.conf.5
202	Typo `umxp`/`umtxp`. This occurs a few more times in this diff.
usr.bin/limits/limits.1
238	All the other limits use the login.conf keyword here. That would suggest changing `process-shared locks` to `umtxp`. Some descriptive text could be added.