You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ Table of Contents
11
11
*[Automatic](#automatic)
12
12
*[Details](#details)
13
13
*[Options](#options)
14
+
*[HTCondor jobs](#htcondor-jobs)
14
15
*[Caveats](#caveats)
15
16
*[bind_condor.sh](#bind_condorsh)
16
17
*[Usage](#usage-1)
@@ -147,10 +148,19 @@ or placed in a file `~/.callhostrc` (automatically detected and sourced by `call
147
148
```bash
148
149
CALL_HOST_STATUS=disable cmssw-el7 ...
149
150
```
151
+
* To enable debug printouts by default:
152
+
```bash
153
+
export CALL_HOST_DEBUG=enable
154
+
```
155
+
or to toggle debug printouts on or off during a session:
156
+
```bash
157
+
call_host_debug
158
+
```
159
+
(if you call this inside a container, it will not silence debug printouts from the host)
150
160
151
-
### Caveats
161
+
### HTCondor jobs
152
162
153
-
* cmslpc autodetection of the correct operating system forjobs is currently based on the host OS. Therefore, if you are submitting jobsin a container with a different OS, you will have to manually specifyin your JDL file (the `X`in`condor_submit X`):
163
+
*On cmslpc, the container OS will automatically be detected (for RHEL-based containers) and used forHTCondor jobs. To specify the job OS manually instead, includein your JDL file (the `X`in`condor_submit X`):
154
164
```
155
165
+DesiredOS = SL7
156
166
```
@@ -160,6 +170,9 @@ or placed in a file `~/.callhostrc` (automatically detected and sourced by `call
160
170
+ApptainerImage = "/path/to/your/container"
161
171
```
162
172
* Using the `ENV()`functionin the JDL file may not functionas intended, since it will be evaluated on the host node, rather than inside the container with your environment set up.
173
+
174
+
### Caveats
175
+
163
176
* Commands that require tty input (such as `nano` or `emacs -nw`) will not work with `call_host`.
164
177
* Occasionally, if a command fails (especially when calling multiple commands separated by semicolons), the pipe will break and the terminal will appear to hang. The message "Interrupted system call" may be shown.
165
178
It is necessary to exit and reenter the container (in order to create a new pipe) if this occurs.
0 commit comments