You are right, ctl-s, ctl-q are terminal control characters - xoff, xon IIRC. They stop terminal output. The poster needs either ctl-z which will allow him to stop the process, then resume it later or ctl-c which will kill the merge entirely and then can resume it with emerge resume later.
> On Saturday 14 June 2003 13:17, [EMAIL PROTECTED] wrote: > > Some one please chim in if I am wrong here, but it is my understanding > > that control-s only stops output being displayed to the terminal. It > > won't actually stop things from happening. It is ment if things are > > scrolling to fast and you to stop to read it. Control-Q is its > > counter-part to continue output. > > > > Now it may be possible that these are signals that can be trapped by > > python, but I think they are received in the tty layer and never get > > passed to python. > > > > The only thing that I can think of that can answer this question is > > actually killing the emerge [like w/ control-c], then starting it up > > again w/ emerge --resume. I know the --resume feature is new since 2.47 > > and was ment incase you emerge -e world, although it may have more uses. > > I can also tell you that --resume will have to start from the start of > > the last package it was working on, however it will not redo any that it > > has already finished. > > > > Cheers, > > Mike > > I second that. The --resume option seems to be the only answer, and I've > used it numerous times. Very effective for putting long-winded stuff on > screen. > > Callan -- Brett I. Holcomb AKA Grunt <>< -- [EMAIL PROTECTED] mailing list
