In article <48a3200e$1_1@mk-nntp-2.news.uk.tiscali.com>,
NVangogh wrote:
>
>
>how can you just put a compilation 'on hold' without stopping it by a
>ctrl-c?
>I need to do this cause sometimes if i am compiling a big thing it can
>take hours and the system seems to give priority to compilation process
>slowing EVERYTHING down. If i could just lern how to 'pause' a
>compilation - that would be cool.

ctrl-z stops most anything running.

Restart with "fg".

Ted
--
------
columbiaclosings.com
What's not in Columbia anymore..

In article <48a3200e$1_1@mk-nntp-2.news.uk.tiscali.com>,
NVangogh wrote:
>I need to do this cause sometimes if i am compiling a big thing it can
>take hours and the system seems to give priority to compilation process
>slowing EVERYTHING down. If i could just lern how to 'pause' a
>compilation - that would be cool.

man 1 nice/man 8 renice
--
Melinda Shore - Software longa, hardware brevis - shore@panix.com

Prouder than ever to be a member of the reality-based community

NVangogh wrote:
> I need to do this cause sometimes if i am compiling a big thing it can
> take hours and the system seems to give priority to compilation process
> slowing EVERYTHING down. If i could just lern how to 'pause' a
> compilation - that would be cool.

Others have already mentioned (re)nice and CTRL-Z. Also pretty handy
ist XON/XOFF - for instance to freeze quickly scrolling output.
Usually CTRL-s to stop the terminal and CTRL-q to continue. Be aware
that processes are only stopped when they try to write to the controlling
terminal.

cu
Clemens.
--
/"\ http://czauner.onlineloop.com/
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \ AND POSTINGS

NVangogh wrote:
> how can you just put a compilation 'on hold' without stopping it by a
> ctrl-c?
> I need to do this cause sometimes if i am compiling a big thing it can
> take hours and the system seems to give priority to compilation process
> slowing EVERYTHING down. If i could just lern how to 'pause' a
> compilation - that would be cool.

There is one further suggestion: use the STOP/CONT signals, with the
kill(1) command.


Interrupt the program with:

$ kill -s STOP $pid

Then do whatever, then restart the program with:

$ kill -s CONT $pid

HTH.
--
Michaël