On 27 Mar 2005, at 4:28 pm, Robert T Wyatt wrote:
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 learned about screen from this article:
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
On Tue, Mar 29, 2005 at 02:32:50AM -0600, Juan Courcoul wrote:
On Mar 27, 2005, at 9:57 AM, Clemence Magnien wrote:
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
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
... and also 'renice' for changing the niceness of running processes.
Robert T Wyatt wrote:
Still, there is nice (note the second sentence, from 'man nice'):
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on
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
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).
On Mar 27, 2005, at 10:28, Robert T Wyatt wrote:
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.)
Basic usage is to run 'screen' to get a new shell inside a screen
session. Inside
On Mar 27, 2005, at 11:02 AM, Matthew Sachs wrote:
On Mar 27, 2005, at 10:28, Robert T Wyatt wrote:
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.)
Basic usage is to run 'screen' to
Clemence Magnien wrote:
So if you run :
$ nohup some_command output_file
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
Matthew Sachs wrote:
On Mar 27, 2005, at 10:28, Robert T Wyatt wrote:
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.)
Basic usage is to run 'screen' to get a new shell inside a screen
On Mar 27, 2005, at 11:30, Robert T Wyatt wrote:
SNIP: screen
So this will also survive a loss of the (parent) SSH connection.
Sounds too good to be true!
It will survive.
(At first I was afraid, I was petrified / I thought that I could
never live without a PTY...)
On Sun, Mar 27, 2005 at 10:27:58AM -0600, Robert T Wyatt wrote:
Clemence Magnien wrote:
So if you run :
$ nohup some_command output_file
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
At 9:28 -0600 27/3/05, 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
On Mar 27, 2005, at 11:27 AM, Robert T Wyatt wrote:
Clemence Magnien wrote:
So if you run :
$ nohup some_command output_file
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
Kyle,
Since my home computer is shared with my significant other, we
frequently need to use the computer while fink is compiling the
sometimes hundreds of packages during the hours/days that it takes to do
this.
I have found that prefixing the commands with 'nice' (see 'man nice') is
Robert T Wyatt robert.wyatt at austin.utexas.edu writes:
[snip]
I have found that prefixing the commands with 'nice' (see 'man nice') is
satisfactory for our general purposes.
[snip]
Thanks for the suggestion to try nice-ing my fink priority down. I
greatly appreciate your help! I've done
Still, there is nice (note the second sentence, from 'man nice'):
nice runs utility at an altered scheduling priority. If an increment is
given, it is used; otherwise an increment of 10 is assumed. The
super-
user can run utilities with priorities higher than normal by using
a neg-
On Mar 26, 2005, at 4:50 PM, Kyle Skrinak wrote:
Robert T Wyatt robert.wyatt at austin.utexas.edu writes:
[snip]
I have found that prefixing the commands with 'nice' (see 'man nice')
is
satisfactory for our general purposes.
[snip]
Thanks for the suggestion to try nice-ing my fink priority down.
On Mar 26, 2005, at 8:43 PM, Aaron Davies wrote:
On Mar 26, 2005, at 4:50 PM, Kyle Skrinak wrote:
Robert T Wyatt robert.wyatt at austin.utexas.edu writes:
[snip]
I have found that prefixing the commands with 'nice' (see 'man
nice') is
satisfactory for our general purposes.
[snip]
Thanks for
Understood everything but this (and thanks for the comments):
Chris Zubrzycki wrote:
Use 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
21 matches
Mail list logo
