You could also take a look at the SSH config. There are two files to check:
/etc/ssh_config
/etc/sshd_config

Look for anything in those files that might be preventing standard (non-root) users from issuing remote commands or that might mess with command paths.

FYI, I’m using the standard settings with no modifications.

Also:
man ssh
man ssh_config
man sshd_config

Might provide clues.

-systemsboy

thanks in advance

You are showing me the sshd_config file, which is for configuring the SSH daemon, not user properties.

If you want to change the user’s home directory, you’d do that in /etc/passwd, I believe (Linux experts correct me if I’m wrong).

-systemsboy

i have ssh ftp configure

in my server one user is there

/home/services/DAILY
how can i put path
linux centos5

# $OpenBSD: sshd_config,v 1.73 2005/12/06 22:38:28 reyk Exp $

# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.

#PATH=/home/services/DAILY

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options change a
# default value.

#Port 22
#Protocol 2,1
Protocol 2
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 768

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
SyslogFacility AUTHPRIV
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6

#RSAAuthentication yes
#PubkeyAuthentication yes
#AuthorizedKeysFile .ssh/authorized_keys

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don’t trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
#59.90.131.411
# Don’t read the user’s ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
PasswordAuthentication yes

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
GSSAPIAuthentication yes
#GSSAPICleanupCredentials yes
GSSAPICleanupCredentials yes

# Set this to ‘yes’ to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication mechanism.
# Depending on your PAM configuration, this may bypass the setting of
# PasswordAuthentication, PermitEmptyPasswords, and
# “PermitRootLogin without-password”. If you just want the PAM account and
# session checks to run without PAM authentication, then enable this but set
# ChallengeResponseAuthentication=no
#UsePAM no
UsePAM yes

# Accept locale-related environment variables
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#ShowPatchLevel no
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
#ChrootDirectory none

# no default banner path
Banner /home/services/DAILY

# override default of no subsystems
Subsystem sftp /usr/libexec/openssh/sftp-server

On the note of the ssh timeout, you could precede every command with a netcat sequence to see if the host is accessible. Something like:
nc -z hostname 22 -w 2

If you get the string “Success!” the server is up and accepting connections on port 22, the return code will (should) be 0. If the server doesn’t respond it will time out after 2 seconds and the return code will (should) be 1.

Maybe use an if statement inside your for loop? (example is written in BASH)
for i in ${serverList[@]};
do
nc -z -w 2 $i 22;
if [ $? == 0 ];
then ssh $i ‘uptime’ >> uptime.log;
else echo “Host is down” >> error.log;
fi
done

This will almost do what it looks like you wanted. Adapting it for Python shouldn’t be difficult, but I did it with BASH as that is what I’m most fluent with. It needs some clean up for things like hostnames in the uptime and error logs and such, but should help provide some direction.

Also if you setup ssh keys then you wont have to worry about entering the password every time.

If the run command is only “screen -dr” the detaching from the screen session would also log you out. Ouch. I personally use “screen -dr && bash -i” as the command to run. It’s not the most beautiful approach but seems to work.

Why do I want it? I run screen+irssi on a remote server. Whenever my internet connection breaks for long enough time for the ssh session to break, I want to be able to reconnect and be ready for IRC business as soon as possible with as little hassle as possible

Timeout is in seconds.

The end of the command should not log you out of the Terminal. It should only log you out of the machine you’re SSHing to. If you don’t want to log out of that machine, there’s not really any reason to use this method. Just SSH into the machine and run your command(s). Then log out when you’re good and ready.

Or, to answer your question more directly, I don’t know of a way to do this, but I don’t really know why you’d need to either.

-systemsboy