public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: rebuilding with -e -- problem with output
Date: Sat, 06 Aug 2005 13:17:26 -0700	[thread overview]
Message-ID: <42F51AD6.10102@gmail.com> (raw)
In-Reply-To: <42F50BE1.2080403@sonic.net>

Raymond Lillard wrote:
> Mark Shields wrote:
> 
>> Perhaps I wasn't clear enough (I apologize, I was only waking up
>> then).  I changed my make.conf file yesterday and starting recompiling
>> my entire system with emerge -ve world &.  I used the & because I was
>> at work and didn't want the recompile process stopping if my ssh
>> session was terminated unexpectedly.  It's still compiling today as I
>> see pktstat is running, but I want to be able to see the output.  Is
>> there a way to recapture the output to screen or to a file?
> 
> 
> Not that I know of now.
> 
> If asked in advance of starting the "emerge", I would have
> advised you to use "nohup".
> 
> man nohup
> 

I'm not aware of a way to reconnect with stderr, stdin, and stdout but I know that those file descriptors still exist in /proc/${PID}/fd.

Normally, in order to accomplish what you want, I would use app-misc/screen.  Screen is a very nice solution because you can reattach to an interactive terminal whenever you want.

Alternatively, you can redirect the emerge output to a log file:

emerge foo > /var/log/emerge-foo.log 2>&1 &

Zac
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-08-06 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06 13:24 [gentoo-user] rebuilding with -e -- problem with output Mark Shields
2005-08-06 13:34 ` [gentoo-user] " Mark Shields
2005-08-06 14:41   ` Mark Shields
2005-08-06 19:13     ` Raymond Lillard
2005-08-06 20:17       ` Zac Medico [this message]
2005-08-06 20:57         ` Raymond Lillard
2005-08-08  9:00           ` Michael Kintzios
2005-08-08  9:37             ` Michael Kintzios

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42F51AD6.10102@gmail.com \
    --to=zmedico@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox