From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NrKIy-0007St-KM for garchives@archives.gentoo.org; Tue, 16 Mar 2010 00:06:40 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 49DFEE0C6F for ; Tue, 16 Mar 2010 00:06:40 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id 23838E0BBD for ; Mon, 15 Mar 2010 23:17:34 +0000 (UTC) Received: from zaphod.digimed.co.uk (zaphod.digimed.co.uk [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.digimed.co.uk (Postfix) with ESMTPSA id 598FF5D2DF9 for ; Mon, 15 Mar 2010 23:17:33 +0000 (GMT) Date: Mon, 15 Mar 2010 23:17:32 +0000 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] what's wrong with rsync 3.0.6? Message-ID: <20100315231732.5cbfe102@zaphod.digimed.co.uk> In-Reply-To: <20100315231041.56f8640b@karnak.local> References: <20100315231041.56f8640b@karnak.local> Organization: Digital Media Production X-Mailer: Claws Mail 3.7.5cvs33 (GTK+ 2.18.7; x86_64-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/JTeqlQhB.J3RN9OShjtBW2X"; protocol="application/pgp-signature" X-Archives-Salt: 71c4419b-aa72-44f2-9f86-29a2b5907606 X-Archives-Hash: f1300239ac5f20680f8ccc8772db978c --Sig_/JTeqlQhB.J3RN9OShjtBW2X Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 15 Mar 2010 23:10:41 +0000, David W Noon wrote: > > Also, for builds, there is such a > >thing as elogs (which allows you to save all messages to=20 > >/var/log/portage for ease of reading at your leisure. =20 >=20 > I have mine go to /var/log/portage/log. But these only log the > activities within a single ebuild, not the other housekeeping that goes > on in an emerge job. The output of a batch job contains the lot. As do the log files in $PORT_LOGDIR, they contain exactly the same output you would see in the terminal. I emerge packages with the -j 2 option, which hides all the output unless an ebuild fails, but it is still in the logs. Elog information is mailed to me. --=20 Neil Bothwick One of the nice things about standards is that there are so many of them. --Sig_/JTeqlQhB.J3RN9OShjtBW2X Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkuewAwACgkQum4al0N1GQPKswCgiHP9b4dA1+Gj3qutDJjrl12k xK0AoI/mFaCh4LUogodrrLE0C8GglAJS =48wK -----END PGP SIGNATURE----- --Sig_/JTeqlQhB.J3RN9OShjtBW2X--