From 3d08cd331c1adcf0d917392f7e527b3f00511748 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Fri, 24 May 2024 06:52:22 +0200 Subject: Merging upstream version 6.8. Signed-off-by: Daniel Baumann --- man5/proc_pid_environ.5 | 48 ------------------------------------------------ 1 file changed, 48 deletions(-) delete mode 100644 man5/proc_pid_environ.5 (limited to 'man5/proc_pid_environ.5') diff --git a/man5/proc_pid_environ.5 b/man5/proc_pid_environ.5 deleted file mode 100644 index 104cbe0..0000000 --- a/man5/proc_pid_environ.5 +++ /dev/null @@ -1,48 +0,0 @@ -.\" Copyright (C) 1994, 1995, Daniel Quinlan -.\" Copyright (C) 2002-2008, 2017, Michael Kerrisk -.\" Copyright (C) 2023, Alejandro Colomar -.\" -.\" SPDX-License-Identifier: GPL-3.0-or-later -.\" -.TH proc_pid_environ 5 2023-08-15 "Linux man-pages 6.7" -.SH NAME -/proc/pid/environ \- initial environment -.SH DESCRIPTION -.TP -.IR /proc/ pid /environ -This file contains the initial environment that was set -when the currently executing program was started via -.BR execve (2). -The entries are separated by null bytes (\[aq]\e0\[aq]), -and there may be a null byte at the end. -Thus, to print out the environment of process 1, you would do: -.IP -.in +4n -.EX -.RB "$" " cat /proc/1/environ | tr \[aq]\e000\[aq] \[aq]\en\[aq]" -.EE -.in -.IP -If, after an -.BR execve (2), -the process modifies its environment -(e.g., by calling functions such as -.BR putenv (3) -or modifying the -.BR environ (7) -variable directly), -this file will -.I not -reflect those changes. -.IP -Furthermore, a process may change the memory location that this file refers via -.BR prctl (2) -operations such as -.BR PR_SET_MM_ENV_START . -.IP -Permission to access this file is governed by a ptrace access mode -.B PTRACE_MODE_READ_FSCREDS -check; see -.BR ptrace (2). -.SH SEE ALSO -.BR proc (5) -- cgit v1.2.3