Re: Fifo buffer question

2014-02-08 Thread Joshua Judson Rosen
ght of reading this message. > > Sent via the Samsung GALAXY S®4, an AT&T 4G LTE smartphone > > Original message > From: Michael ODonnell > Date: 02/06/2014 18:14 (GMT-05:00) > To: gnhlug-discuss@mail.gnhlug.org > Subject: Re: Fifo buffer question >

Re: Fifo buffer question

2014-02-06 Thread jburtram
Agreed - screen was the first thing I thought of reading this message.  Sent via the Samsung GALAXY S®4, an AT&T 4G LTE smartphone Original message From: Michael ODonnell Date: 02/06/2014 18:14 (GMT-05:00) To: gnhlug-discuss@mail.gnhlug.org Subject: Re: Fifo bu

Re: Fifo buffer question

2014-02-06 Thread Michael ODonnell
Ah! forgot about that screen/tmux approach (screen, in my case) - I, too, have had good results with it, circumstances permitting... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss

Re: Fifo buffer question

2014-02-06 Thread Chris Linstid
On Thu, Feb 6, 2014 at 3:48 PM, Kevin D. Clark wrote: > Sometimes I leave long-running compute jobs running under screen. > Start them in one physical location. Later, in some other location, I > re-attach and look at my output. > I've done the same at my last few jobs when I had a long build (

Re: Fifo buffer question

2014-02-06 Thread Kevin D. Clark
Curt Howland writes: > I have a background process running from which I would like, from time > to time, to check the console output. I do not want to dedicate a > console window to it, and since I start it from a script the console > output is usually just lost to the akashic ethers. [...] > S

Re: Fifo buffer question

2014-02-06 Thread r270
Background processes don't generally send output to the console, because they are not associated with a console. If you just want to see if it's running: ps -x | egrep 'MyProcessName' If you want to temporarily bring a background process to the foreground, use the "fg" bash builtin. As Chris s

Re: Fifo buffer question

2014-02-06 Thread Michael ODonnell
> Could I start the process with " > fifo-buffer.txt" and then > when I want to check the output, run a "tail -f fifo-buffer.txt" If your fifo-buffer.txt is a plain file that isn't managed (log rotation, etc) then the risk is that it wastes or exhausts disk space. If it's a named pipe any write

Re: Fifo buffer question

2014-02-06 Thread Chris Linstid
On Thu, Feb 6, 2014 at 2:57 PM, Thomas Charron wrote: > Use the right tool for the job. multilog is a utility which you pipe > your stdout/err to, and it maintains logs, including log rotation, etc.. > So it can be spewing out all the time, but you can have say, 3 logs based > on 100k each. >

Re: Fifo buffer question

2014-02-06 Thread Thomas Charron
Use the right tool for the job. multilog is a utility which you pipe your stdout/err to, and it maintains logs, including log rotation, etc.. So it can be spewing out all the time, but you can have say, 3 logs based on 100k each. On Thu, Feb 6, 2014 at 2:34 PM, Curt Howland wrote: > Good aft

Re: Fifo buffer question

2014-02-06 Thread Chris Linstid
> > I have a background process running from which I would like, from time > to time, to check the console output. I do not want to dedicate a > console window to it, and since I start it from a script the console > output is usually just lost to the akashic ethers. > > I've not played with fifo bu

Fifo buffer question

2014-02-06 Thread Curt Howland
Good afternoon. I have a background process running from which I would like, from time to time, to check the console output. I do not want to dedicate a console window to it, and since I start it from a script the console output is usually just lost to the akashic ethers. I've not played with fif