Page MenuHomeFreeBSD

Document procfs(5) as obsolete
AcceptedPublic

Authored by trasz on Thu, Nov 7, 2:33 PM.

Details

Reviewers
emaste
bcr
Group Reviewers
manpages
Summary

Update the procfs(5) man page to clarify that it's obsolete.

Diff Detail

Repository
rS FreeBSD src repository
Lint
Lint OK
Unit
No Unit Test Coverage
Build Status
Buildable 27388
Build 25635: arc lint + arc unit

Event Timeline

trasz created this revision.Thu, Nov 7, 2:33 PM
bcr accepted this revision.Thu, Nov 7, 2:39 PM
bcr added a subscriber: bcr.

Bump the .Dd when you commit. Thanks!

This revision is now accepted and ready to land.Thu, Nov 7, 2:39 PM
emaste added a comment.Thu, Nov 7, 2:44 PM

Do we know what if any ports actually use procfs?

Do we know what if any ports actually use procfs?

Quite a lot of software ported from Linux, because it's way easier to change /proc/self to /proc/curproc than to actually write code for using sysctls and such :)

Grepping for curproc in ports reveals x11/keyboardcast, security/beid, net-mgmt/seafile-server, net-mgmt/seafile-client, java/openjdk7, net-mgmt/ccnet-server, mail/dbmail, science/opensph, sysutils/memfetch, devel/RStudio, devel/synfig, devel/clanlib1, devel/clanlib, devel/oclgrind… Typically it's just for finding the current executable binary.

And you can find more on the internet e.g.

Just installed libsigsegv on a machine and the pkg message was: "Note that the stackoverflow handling functions of this library need procfs mounted on /proc."

trasz added a comment.Fri, Nov 8, 11:04 AM

So... Is procfs actually obsolete then?

emaste added a comment.Fri, Nov 8, 5:33 PM

So... Is procfs actually obsolete then?

I would say use of procfs is deprecated, and your advice (about libkvm etc.) is sound., but it is still used by a number of ports.