On Mar 27, 2005, at 9:57 AM, Clemence Magnien wrote:
On Sun, Mar 27, 2005 at 09:28:59AM -0600, Robert T Wyatt wrote: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?
I don't know anything about screen, but maybe this tip can help you: the nohup command allows you to run a process in the background, and prevent this process to be killed if its parent (i.e. the term it was launched from) terminates.
So if you run : $ nohup some_command > output_file &
Aren't you missing a 2>&1 in there? Cause in bash this will only save standard output but not standard error.
this will run 'some_command', store its standard and error output in 'output_file', and it runs in the background, so you can do whatever you like with your term, like doing something else, closing it. You can also shut X11 down and logout, this will not prevent your command from running.
------------------------------------------------------- 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
