Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Guest

OK,
i found the solution.... i had to put "call" before:

winscp> call ls -la
total 92
drwxr-x--- 6 root wheel 306 Dec 28 21:13 .
drwxr-xr-x 24 root wheel 884 Dec 8 22:18 ..
-rw------- 1 root wheel 5542 Dec 25 19:27 .bash_history
-rw------- 1 root wheel 35 Dec 11 16:45 .lesshst
drwxr-x--- 8 root wheel 272 Dec 10 12:05 Library
drwxr-xr-x 2 root wheel 68 Jul 20 03:14 Media
drwxr-xr-x 3 root wheel 136 Dec 28 17:40 gg
-rw------- 1 root wheel 78205 Dec 25 18:35 iopd.log
drwxr-xr-x 2 root wheel 68 Dec 28 21:13 zz


thanks anyway
shtofff

How run "ls -la" ?

Hi,
i'm running from command-line:
C:\Program Files\WinSCP>WinSCP.com root:mypassword@127.0.0.1:22

and when trying to run "ls -la" i'm getting Unknown command error:

winscp> ls -la
Unknown switch 'la'.

how can i solve it when running from command-line ?
martin

Re: ls --full-time does not work on command-line

WinSCP is not SSH terminal, it is SFTP client. You cannot execute remote command this way. 'ls' is local command of the client. It can no options like '--fulltime'.

Anyway what do you miss in timestamp WinSCP displays?
Torsten

ls --full-time does not work on command-line

Hi,

I connected to a server via command-line using the latest winscp-version. I tried the command "ls" which works. But I want to have the full timestamp and so I tried "ls --full-time" which does not work

winscp> ls --fulltime
Error listing directory '--fulltime'.
Command 'ls -la "./--fulltime"'
failed with return code 2 and error message
./--fulltime: No such file or directory.
(A)bort, (R)etry, (S)kip: Skip
...
winscp> ls -la -full-time
Too many parameters for command 'ls'.

What is the mistake?

Thanks.

Regards,
Torsten