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?
Yes, you could quit Terminal after you detach the screen session (Ctrl-a d). But I don't think that the Terminal uses much CPU time after you detach the screen session, so I usually leave it running. Activity Monitor seems to show that Terminal uses less than 0.5% CPU just sitting there.
Kevin Horton
------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
