This is neat-hadn't heard of it before. The man page is huge and I'd like to get more familiar with setting screen to run fink compilations routing the log to a file (I understand this saves overhead on the display or buffer). There have been oblique references to detaching the session from Terminal so as to save the 7-8% cpu that it sucks up, does this mean that Terminal can be quit after spawning screen?

Anyhow, do y'all know of a Web site or discussion list or a primer somewhere? (I did not find one in the man page, only the e-mail address of the developer.)

I know that part of these questions have been answered below, but usage examples are golden to a fellow like myself.

Thanks again!

Kevin Horton wrote:
At 22:15 -0600 26/3/05, Robert T Wyatt wrote: Understood everything but this (and thanks for the comments):

Chris Zubrzycki wrote: Use screen

I use screen quite a bit, as it puts the fink install stuff in the background, rather than having it continually update a Terminal window. I can also log in from my laptop to see how things are going with the install on the main computer.

To start a new screen session:
screen -R

To save the output from the current session to a log file:
Ctrl-a H

To stop logging:
Ctrl-a H

To detach the current screen session (i.e. return to the original Terminal window, but have whatever was going on in screen continue, unseen):
Ctrl-a d


To reattach a screen session (from the same computer, or from another one that you are ssh'd in from):
screen -R


There are many more options - see man screen.



------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to