Unexpected directory listing line "drwxr-x--- 27 bofh users 4096 2003-10-24 13:43 .".

Hi I have problems using winscp when connecting to the new SUSE 8.2 server when the user has tcsh as login shell. I get the following error message.

Error listing directory "/home/bofh". Unexpected directory listing line "drwxr-x--- 27 bofh users 4096 2003-10-24 13:43 .". Operation aborted

However it works nicely if the user has bash as login shell. Is there any way to configure winscp to work with tcsh.

Thanks in advance
/Jonas

This particular problem with tcsh may be solved. But in general WinsCP will not work with tcsh, because the shell behaves incorrectly with non-interactive shell (WinSCP case).
You may specify /bin/bash shell on SCP tab of login dialog. So you may keep tcsh as default user shell.
And of course, you may use SFTP instead of SCP. SFTP is not influenced by user shell. Next version (very soon), will have much better performance with SFTP that current version.

martin wrote:

This particular problem with tcsh may be solved. But in general WinsCP will not work with tcsh, because the shell behaves incorrectly with non-interactive shell (WinSCP case).
You may specify /bin/bash shell on SCP tab of login dialog. So you may keep tcsh as default user shell.
And of course, you may use SFTP instead of SCP. SFTP is not influenced by user shell. Next version (very soon), will have much better performance with SFTP that current version.

While SFTP does work, I have also found SCP failing with the same response "Unexpected directory listing line "drwxr-xr-x 16 jochs jochs 544 6 Oct 12:33 .". Operation aborted". However, this persists even when my shell is manually set to /bin/bash. This is connecting to Mac OS X 10.3 (Panther). Connecting to OS X 10.2 always worked with SCP, even with tcsh.

I have noticed some other oddities in 10.3's SSH - it doesn't seem to support resolving "localhost" to "127.0.0.1" in putty like 10.2 used to, even though my hosts file specifies it properly.

Joshua Ochs wrote:

martin wrote:

This particular problem with tcsh may be solved. But in general WinsCP will not work with tcsh, because the shell behaves incorrectly with non-interactive shell (WinSCP case).
You may specify /bin/bash shell on SCP tab of login dialog. So you may keep tcsh as default user shell.
And of course, you may use SFTP instead of SCP. SFTP is not influenced by user shell. Next version (very soon), will have much better performance with SFTP that current version.

While SFTP does work, I have also found SCP failing with the same response "Unexpected directory listing line "drwxr-xr-x 16 jochs jochs 544 6 Oct 12:33 .". Operation aborted". However, this persists even when my shell is manually set to /bin/bash. This is connecting to Mac OS X 10.3 (Panther). Connecting to OS X 10.2 always worked with SCP, even with tcsh.

I have noticed some other oddities in 10.3's SSH - it doesn't seem to support resolving "localhost" to "127.0.0.1" in putty like 10.2 used to, even though my hosts file specifies it properly.

Here are the SSH versions:

10.2: OpenSSH_3.4p1+CAN-2003-0693, SSH protocols 1.5/2.0, OpenSSL 0x0090609f
10.3: OpenSSH_3.6.1p1+CAN-2003-0693, SSH protocols 1.5/2.0, OpenSSL 0x0090702f

Joshua Ochs wrote:

martin wrote:

This particular problem with tcsh may be solved. But in general WinsCP will not work with tcsh, because the shell behaves incorrectly with non-interactive shell (WinSCP case).
You may specify /bin/bash shell on SCP tab of login dialog. So you may keep tcsh as default user shell.
And of course, you may use SFTP instead of SCP. SFTP is not influenced by user shell. Next version (very soon), will have much better performance with SFTP that current version.

While SFTP does work, I have also found SCP failing with the same response "Unexpected directory listing line "drwxr-xr-x 16 jochs jochs 544 6 Oct 12:33 .". Operation aborted". However, this persists even when my shell is manually set to /bin/bash. This is connecting to Mac OS X 10.3 (Panther). Connecting to OS X 10.2 always worked with SCP, even with tcsh.

I have noticed some other oddities in 10.3's SSH - it doesn't seem to support resolving "localhost" to "127.0.0.1" in putty like 10.2 used to, even though my hosts file specifies it properly.

It appears there is a new column in the ls command for 10.3:

10.2:
drwxr-xr-x 26 jochs staff 884 Oct 25 21:37 .
drwxrwxr-t 6 root wheel 204 Jun 15 23:26 ..

10.3:
drwxr-xr-x 16 jochs jochs 544 6 Oct 12:33 .
drwxrwxr-t 5 root admin 170 5 Oct 21:54 ..

Joshua Ochs wrote:

It appears there is a new column in the ls command for 10.3:

10.2:
drwxr-xr-x 26 jochs staff 884 Oct 25 21:37 .
drwxrwxr-t 6 root wheel 204 Jun 15 23:26 ..

10.3:
drwxr-xr-x 16 jochs jochs 544 6 Oct 12:33 .
drwxrwxr-t 5 root admin 170 5 Oct 21:54 ..

Final bit of spam - it's not a new column - the new "ls" just seems to list the day before the month, that's all. Strange.

I would still recommend trying SFTP instead of SCP.

Are there any options or workarounds in WinSCP that will instruct it to ignore the reversed date listing in 10.3 ? Alternatively, is there a way to instruct "ls" on 10.3 to use the old date format? 10.3 does not have SFTP.

WinSCP cannot read date in this format. I suppose that there must be a way how to force 10.3 to use standard format.

Guest wrote:

Are there any options or workarounds in WinSCP that will instruct it to ignore the reversed date listing in 10.3 ? Alternatively, is there a way to instruct "ls" on 10.3 to use the old date format? 10.3 does not have SFTP.

Had the same problem when upgraded to Panther. Try SFTP but set SSH2 as the preferred protocol. Should work then.

martin wrote:

WinSCP cannot read date in this format. I suppose that there must be a way how to force 10.3 to use standard format.

Unfortunately, this is a bug in 10.3. I filed a radar, #3473836, which looks like it will be fixed in some upcoming 10.3.x release.

Anonymous wrote:

martin wrote:

WinSCP cannot read date in this format. I suppose that there must be a way how to force 10.3 to use standard format.

Unfortunately, this is a bug in 10.3. I filed a radar, #3473836, which looks like it will be fixed in some upcoming 10.3.x release.

One workaround is to install Color LS in Panther.
Worked fine for me, download it from here:
<invalid hyperlink removed by admin>

Guest wrote:

10.3 does not have SFTP.

10.3 does have SFTP. I just tried it.

For the reversed day/month problem: Workaround is to use SFTP instead of SCP. Reportedly this has been files as a bug on Mac OS X 10.3 (Panther). Refer here.

For list of reasons WinSCP cannot parse directory listing and possible resolutions, see documentation.