RE: [gentoo-user] Re: rebuilding with -e -- problem with output

["Michael Kintzios" <michaelkintzios@lycos.co.uk>]

> -----Original Message-----
> From: Raymond Lillard [mailto:rlillard@sonic.net] 
> Sent: 06 August 2005 21:57
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] Re: rebuilding with -e -- problem 
> with output
> 
> 
> Zac Medico wrote:
> > 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".
> > 
> > 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.
> 
> Good idea.
> 
> > Alternatively, you can redirect the emerge output to a log file:
> > 
> > emerge foo > /var/log/emerge-foo.log 2>&1 &
> 
> All true, but the point of using "nohup" is that it disassociates
> the nohup'd process from the parent shell/terminal session.  This
> allows one to start a long running task and log out without ending
> it.  Pushing a task into the background followed by a logout will
> end said background task.
> 
> Progress may be monitored by logging in at some later point in
> time and/or from some other location.  "tail -f" works well for
> this.
> 
> -- 
> Regards,
> Ray

In addition to the above there's also PORTAGE_LOG="/var/log/portage"
which can be set in the /etc/make.conf to capture the emerge proceedings
by tee-ing into the relevant file in /var/log/portage.  Again, using
tail -f in this file(s) will show you what's happening.  Setting up
logrotate or a cron jobby will help to keep the /var/log/portage
directory under control before it bloats itself to destruction. ;)
-- 
Regards,
Mick

-- 
gentoo-user@gentoo.org mailing list