Subject: [HTCondor-users] question about condor_ssh_to_job behavior
Dear all,
we are running the HTCondor EP daemons in an apptainer container and
submitting jobs running themselves in a container.
I would like to ask you some questions about the behavior of
condor_ssh_to_job.
1) At the beginning of the session, I got the following message.
Welcome to slot1@test-condor@c4p-login-dev!
Your condor job is running with pid(s) 67581.
Cannot chdir to /var/lib/condor/execute/dir_67539: No such
file or directory
Singularity>
Is the message "Cannot chdir to /var/lib/condor/execute/dir_67539:
No such file or directory" expected?
The directory exists, the job is executed properly, and I can see in
the StarterLog:
After that, the exit process is pending, and a CTRL C is needed to
close the session.
3) Is there some way to optimise the environment?
  I was not able to make the completion work, neither the delete,
or the navigation in the commands history.
ÂÂÂ I guess I am missing something in my configuration of
condor_ssh_to_job.
Starting session: forced-command (key-option)
'/usr/libexec/condor/condor_ssh_to_job_shell_setup
/var/lib/condor/execute/dir_67539/.condor_ssh_to_job_1/env.sh' for
benoit_roland from 2a00:139c:3:2e5::12 port 24035 id 0
Is there a way to further configure the environment which is setup
by the above command line?