title: How to determine if a cp process in terminal (command line) is stuck?
body: <p>I've forced myself into the habit of utilizing the command line "cp" command on my OS X machines to copy over large directories rather than the usual "click and drag" method. However, for the first time it seems like the process might be stuck.</p>
  
  <p>I've used the Ctrl + t command during the process to determine if something is still active. It's output is as shown below:</p>
  
  <pre><code>load: 1.79  cmd: cp 657 running 23.54u 422.25s
  load: 1.73  cmd: cp 657 running 23.54u 422.25s
  load: 1.91  cmd: cp 657 running 23.54u 422.25s
  load: 1.97  cmd: cp 657 running 23.54u 422.25s
  load: 1.34  cmd: cp 657 running 23.54u 422.25s
  load: 1.33  cmd: cp 657 running 23.54u 422.25s
  </code></pre>
  
  <p>Please note that the output above was generated by the ctrl + t command at intervals with a few minutes in between. I'm starting to lean towards it being stuck given the "running ..." being the same in each line.</p>
  
  <p>Should I just cancel the process via ctrl + c and start over with a merge cp command?</p>
  
  <p>Any help on this is greatly appreciated.</p>