Ready to be published? LXer is read by around 350,000 individuals each month, and is an excellent place for you to publish your ideas, thoughts, reviews, complaints, etc. Do you have something to say to the Linux community?
Let’s say you’re editing a configuration file in the Linux “vi” editor, and suddenly need to look up some data in another file? On a regular GUI system, this wouldn’t be a problem. You just open the second file, check when you need, and then switch back to the first program. On a command line, it isn’t that simple.
We all know that if a process is misbehaving, ctrl+c just shuts it down. Either a program is running for too long, or it’s leaving a huge output that’s scrolling by faster than you can see it! Pressing Ctrl+c aborts the process immediately with something called a SIGINT signal. This tells the process to wrap up what it’s doing and abort immediately.
In most cases, this works, but keep in mind that it’s up to each process to decide how to handle it. Some processes like vi ask for confirmation before exiting – usually with good reason since aborting without warning can lead to data loss or corruption.
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
