Frankly, I didn't notice the difference between CTRL Z and CTRL C, because when I pressed it, I found that the current running commands stopped, and they seemed to function the same.
But recently when writing the socket program found that the server short use of CTRL C to end all normal, the next boot is normal. When using Ctrl Z to finish, it is found that the address is already occupied when it starts again, meaning that the port cannot start the new service.
At this point my first reaction is: is not the CTRL Z end what resources are not recycled?
Check the next to know that the Ctrl z does not really quit, but just put the command executed in the foreground in the background , this is what I use the socket client to send content or normal, this time can use jobs to view the background running program, the display is running.
At this time with FG to the background running Cheng put to the front desk, echo what is normal.