This is probably not a direct answer to what you’re asking, but when I need to transfer files over a SSH session I use WinSCP, which is an excellent file transfer program over SCP or SFTP. Of course this assumes you’re on Windows.
The scponly shell may allow the quota command (if enabled). But it seems that you have the scponly configured to support the SFTP only, with a shell access disallowed. The SFTP protocol allows checking disk space (contrary to what other answers say). Extracting from the SFTP – check free space available question of stackoverflow.com: SFTP … Read more
It’s a common pitfall: All folders up to the chroot home must be owned and only writable by root user. The folders cannot be group writable – even if the group is root.
SCP is the abbreviation of ‘secure copy’, while SFTP stands for ‘secure FTP’. The first is used to copy one or more files, often with known names, from host A to host B, whereas the second is mostly used interactively, analogue to an FTP client. SCP will always work out of the box and has … Read more
Symlinks are purely symbolic: they contain nothing but a path, so when you open a symlink, the OS reads the path and uses that instead. In a chroot environment, links (especially ones with absolute paths) typically don’t point to the same place they pointed to in the normal environment. If the server OS is Linux, … Read more
Generally including a password in a command line is considered a security risk because it will show up to anyone else who can run ps/top, and it may be saved in your shell’s history. It would be a much better idea to setup key-based authentication if you are able. Also, I don’t believe it is … Read more
Copy multiple files from remote to local: $ scp your_username@remote.edu:/some/remote/directory/\{a,b,c\} ./ Copy multiple files from local to remote: $ scp foo.txt bar.txt your_username@remotehost.edu:~ $ scp {foo,bar}.txt your_username@remotehost.edu:~ $ scp *.txt your_username@remotehost.edu:~ Copy multiple files from remote to remote: $ scp your_username@remote1.edu:/some/remote/directory/foobar.txt \ your_username@remote2.edu:/some/remote/directory/ Source: http://www.hypexr.org/linux_scp_help.php
While TCP port 22 is the general right answer, this is dependent on the fact that SSH is configured to use the standard port and not an alternative port. As SFTP runs as a subsystem of SSH it runs on whatever port the SSH daemon is listening on and that is administrator configurable.