Post History
Why not simply use ls -l on the target file? Or ls -lt | head on the directory? The -lt option makes ls to show long description, including size and timestamp, while sorting by timestamp. So you ...
#2: Post edited
Why not simply use `ls -l` on the target file? Or `ls -lt | head` ?- The `-lt` option makes `ls` to show ***l***ong description, including size and timestamp, while sorting by ***t***imestamp.
- So you can see, from the timestamp, if the command has done recent changes, and from the size, what is the progress.
- Maybe you have to send the `cp` command to the background (preferably by adding an "&" at the end of it, or to open another shell.
- If something looks strange, you can uses `top` or `ps aguwx | grep <yourfilename>` to see if the process is still actve.
- Why not simply use `ls -l` on the target file? Or `ls -lt | head` on the directory?
- The `-lt` option makes `ls` to show ***l***ong description, including size and timestamp, while sorting by ***t***imestamp.
- So you can see, from the timestamp, if the command has done recent changes, and from the size, what is the progress.
- Maybe you have to send the `cp` command to the background (preferably by adding an "&" at the end of it, or to open another shell.
- If something looks strange, you can uses `top` or `ps aguwx | grep <yourfilename>` to see if the process is still actve.
#1: Initial revision
Why not simply use `ls -l` on the target file? Or `ls -lt | head` ? The `-lt` option makes `ls` to show ***l***ong description, including size and timestamp, while sorting by ***t***imestamp. So you can see, from the timestamp, if the command has done recent changes, and from the size, what is the progress. Maybe you have to send the `cp` command to the background (preferably by adding an "&" at the end of it, or to open another shell. If something looks strange, you can uses `top` or `ps aguwx | grep <yourfilename>` to see if the process is still actve.
