Configure command parameters

Advertisement

Hansjörg
Guest

Configure command parameters

Hello,

I'm using WinSCP to access a Linux machine with a busy box (embedded) instead of a full shell. The busy box does not implement all features for all commands.
E.g. the ls command does not support the option --full-time.
Command 'ls -la --full-time'
failed with return code 1 and error message
ls: unrecognized option `--full-time'
BusyBox v1.1.3 (2006.08.10-09:26+0000) multi-call binary
Is there a way to configure the command executed?

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
41,518
Location:
Prague, Czechia

Re: Configure command parameters

WinSCP should try --full-time once and if that fails, it should stop using it. Can you post a complete log file?

Reply with quote

Guest

Re: Configure command parameters

I had the same problem when accessing a PogoPlug running busybox.
Command 'pwd'
failed with return code 0 and error message
ls: unrecognized option '--full-time'
BusyBox v1.16.1 (2010-11-30 12:06:37 PST) multi-call binary.

Usage: ls [-1AacCdeFilnpLRrSsTtuvwxXhk] [FILE]....
For some reason the behavior is persistent and even after the first failure it still uses the --full-time option which is not supported by busybox.

For working around with this problem check these WinSCP settings.
  1. Open the WinSCP login interface
  2. Certify that Advanced Options check box is checked
  3. In the left box click on Session
  4. Then in the right side select File Protocol: SCP
  5. In the left box click on SCP/Shell option (under Environment topic)
  6. If you cannot see the SCP/Shell option return to step 2. This option only shows up if Advanced Options is checked.
  7. Then in the right side unselect the option "Try to Get Full Timestamp" under Directory Listing box.
    if the checkbox is inaccessible return to step 4, you only can change this for SCP protocol.
  8. also unselect the option "Lookup User Groups" under Other Options box
  9. save your new settings
You should be good to go now without any problems.
It took me hours to figure out how to configure this. Many forums talk about that but the configuration process is a bit tricky if you are not familiar to the WinSCP.

Here are some reference forums I used to troubleshooting this issue.
  1. https://winscp.net/eng/docs/ui_login_scp
    Look at Directory Listing topic, it explains that sometimes WinSCP fails in detecting Failure on ls command, that's why you need to manually change the settings.
  2. <invalid hyperlink removed by admin>
  3. <invalid hyperlink removed by admin>
I hope this replay can easily show how to configure WinSCP and workaround with this problem.

Thanks to all,
Marcelino

Reply with quote

Advertisement

You can post new topics in this forum