On Wed, 2007-10-17 at 15:44 -0400, seth vidal wrote: > On Wed, 2007-10-17 at 14:50 -0400, James Antill wrote: > > > Who asked for this, and did they give a problem they are trying to > > solve by it? > > chroot handling from outside.
Right, that's what I thought. > > I think a better solution is to use a different log file when using a > > custom installroot, so maybe they'd be happy with a --logfile cmd line > > option? > > well, when we're operating on a chroot that's already existent we write > to $chroot/var/log/yum.log > > if the chroot isn't there, yet, we write to /var/log/yum.log so that it > gets recorded somewhere. Ok, so this is only relevant when we initially create a chroot ... even more reason not to put it in the default /var/log/yum.log IMO. Just creating a /yum.log in the chroot is probably better. My main problem with it is I don't see how the information is usable, in the main yum.log, for a significant amount of time after the fact. Mainly due to chroot's getting moved after install and/or they'll be loop back mounts which get unmounted. And after we are at the point we have a real chroot it'll use a different log file anyway. So if you have a program that looks through the yum.log file it can only really say "chroot at X installed at roughly Y time". -- James Antill <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
