1CONDOR_PROCD(1)                 HTCondor Manual                CONDOR_PROCD(1)
2
3
4

NAME

6       condor_procd - HTCondor Manual
7
8       Track and manage process families
9
10

SYNOPSIS

12       condor_procd -h
13
14       condor_procd -A address-file [options ]
15

DESCRIPTION

17       condor_procd  tracks  and manages process families on behalf of the HT‐
18       Condor daemons. It may track families of PIDs  via  relationships  such
19       as:  direct parent/child, environment variables, UID, and supplementary
20       group IDs. Management of the PID families include
21
22       • registering new families or new members of existing families
23
24       • getting usage information
25
26       • signaling families for operations such as suspension, continuing,  or
27         killing the family
28
29       • getting a snapshot of the tree of families
30
31       In  a regular HTCondor installation, this program is not intended to be
32       used or executed by any human.
33
34       The required argument, -A address-file, is the path and  file  name  of
35       the address file which is the named pipe that clients must use to speak
36       with the condor_procd.
37

OPTIONS

39          -h     Print out usage information and exit.
40
41          -D     Wait for the debugger. Initially sleep 30 seconds before  be‐
42                 ginning normal function.
43
44          -C principal
45                 The  principal is the UID of the owner of the named pipe that
46                 clients must use to speak to the condor_procd.
47
48          -L log-file
49                 A file the condor_procd will use to  write  logging  informa‐
50                 tion.
51
52          -E     When  specified, another tool such as the procd_ctl tool must
53                 allocate the GID associated with a process. When this  option
54                 is  not specified, the condor_procd will allocate the GID it‐
55                 self.
56
57          -P PID If not specified, the condor_procd will use the  condor_procd
58                 's  parent,  which may not be PID 1 on Unix, as the parent of
59                 the condor_procd and the root of the tracking  family.   When
60                 not  specified,  if  the condor_procd 's parent PID dies, the
61                 condor_procd exits. When  specified,  the  condor_procd  will
62                 track  this  PID  family in question and not also exit if the
63                 PID exits.
64
65          -S seconds
66                 The maximum number of seconds the condor_procd will wait  be‐
67                 tween  taking  snapshots  of  the tree of families. Different
68                 clients to the condor_procd can  specify  different  snapshot
69                 times. The quickest snapshot time is the one performed by the
70                 condor_procd. When this option is not  specified,  a  default
71                 value of 60 seconds is used.
72
73          -G min-gid max-gid
74                 If  the  -E option is not specified, then track process fami‐
75                 lies using a self-allocated, free GID out  of  the  inclusive
76                 range  specified by min-gid and max-gid. This means that if a
77                 new process shows up using a previously known  GID,  the  new
78                 process  will automatically associate into the process family
79                 assigned that GID.  If the -E option is specified,  then  in‐
80                 stead  of self-allocating the GID, the procd_ctl tool must be
81                 used to associate the GID with the PID root  of  the  family.
82                 The associated GID must still be in the range specified. This
83                 is a Linux-only feature.
84
85          -K windows-softkill-binary
86                 This is the path and  executable  name  of  the  condor_soft‐
87                 kill.exe  binary.  It  is  used  to  send softkill signals to
88                 process families.  This is a Windows-only feature.
89

DEALING WITH SHORT READS

91       For unknown reasons, on Linux, attemps to read the list  of  PIDs  from
92       the  /proc  filesystem do not always return all of the PIDs on the sys‐
93       tem.  The condor_procd attempts to detect when this occurs,  using  two
94       methods.
95
96       If the list of PIDs does not include PID 1, the condor_procd's own PID,
97       or the PID of the condor_procd's parent (which may be PID 1), then  the
98       list  must  be incomplete, and the condor_procd immediately retries the
99       read.
100
101       Additionally, the condor_procd compares the number of PIDs it just read
102       to the number of PIDs from the last time it (successfully) checked.  If
103       the number is too much smaller, it immediately  retries.   The  default
104       threshold is 0.90, meaning that if the current read has 90% or fewer of
105       the last read's PIDs, it's considered invalid.  In  our  testing,  this
106       threshold was met by roughly 1 in 4000 reads, but successfully detected
107       all real short reads.  If you need to adjust the threshold, you may  do
108       so  by setting the environment variable _CONDOR_PROCAPI_RETRY_FRACTION.
109       (In the normal case, simply have it in the environment  when  the  con‐
110       dor_master starts up.)
111
112       If  a retried read is incomplete (according to either method), the con‐
113       dor_procd returns the results of the previous read.
114

GENERAL REMARKS

116       This program may be used in a stand alone mode, independent  of  HTCon‐
117       dor,  to  track process families. The programs procd_ctl and gidd_alloc
118       are used with the condor_procd in stand alone mode to interact with the
119       daemon  and  to inquire about certain state of running processes on the
120       machine, respectively.
121

EXIT STATUS

123       condor_procd will exit with a status value of 0  (zero)  upon  success,
124       and it will exit with the value 1 (one) upon failure.
125

AUTHOR

127       HTCondor Team
128
130       1990-2023,  Center for High Throughput Computing, Computer Sciences De‐
131       partment, University of Wisconsin-Madison, Madison,  WI,  US.  Licensed
132       under the Apache License, Version 2.0.
133
134
135
136
137                                 Oct 02, 2023                  CONDOR_PROCD(1)
Impressum