> From: Garrett D'Amore > Sent: Thursday, October 12, 2017 6:43 PM > Because the notion of cwd for a process may differ based on how a process > got there, and what context it is running in, I would strongly prefer to see > that we take very careful care of this, and if we’re going to make it > universally > available, then let’s do it properly via system call that takes care of any > normalization that might be necessary to account for chroot, zones, etc. > Stashing this away in procfs feels far less “good” to me.
I agree, it should be done "right"; I'm just arguing that it should be done :). As I mentioned, given the implementer, I think it probably was done "right" in Solaris, although I'm not sure what level of observability can be taken from that proprietary operating system to determine how. Presumably at the very least a third-party independent user could report what Solaris getcwd returns in various scenarios such as in a zone or chroot without procfs available. ------------------------------------------ illumos-discuss Archives: https://illumos.topicbox.com/groups/discuss/discussions/T1bf578bf66b8b8b0-M135ba3ce83eb908c9887b9ee Powered by Topicbox: https://topicbox.com
