[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] condor_ssh_to_job
- Date: Wed, 21 Aug 2013 13:14:50 -0500
- From: Brian Bockelman <bbockelm@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] condor_ssh_to_job
In the end, condor_ssh_to_job relies on the ssh binaries and configuration on the worker node. If the sysadmins have disabled SSH logins (either via sshd_config or setting the user's shell to nologin), then condor_ssh_to_job won't work.
To some extent, disabling logins in sshd_config is the admins way of setting "site policy" and condor should obey it. It may be a good idea to talk to your sysadmin.
A purposely limited job-monitoring is "condor_tail". Depending on what you were trying to do, that may be helpful.
On Aug 21, 2013, at 12:39 PM, "Shrum, Donald C" <DCShrum@xxxxxxxxxxxxx> wrote:
> When I try to condor_ssh_to_job I get the message...
> This account is currently not available.
> I'm guessing the job is running as nobody and that there is a setting in condor_config that tells condor to use the id the job was submitted with. I'm looking in the manual now but if someone has a quick answer I would appreciate it.
> FSU Research Computing Center
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: