Oisin C. Feeley wrote: > On Mon, 21 Oct 2002, Paul Gear wrote: > >>Oisin C. Feeley wrote: > > [snip] > >>>In order to try and find where the file was I did an "updatedb; locate >>>kernel-source", ran "lsof -c up2date | grep kernel" all to no avail. >>> >>>The only thing that turned up was the kernel-source.X.hdr. After the >>>kernel-source.rpm package displayed 100% downloaded in the up2date window >>>the kernel-source.X.rpm appeared in /var/spool/up2date. >>> >>>So, does anyone know where are these files stored during the download >>>process? >> >>Out of curiosity, why do you want to know? What difference does it >>make? You can't use them until they're complete anyway. >> > > > Two reasons: > 1. I want to go back to using "up2date-nox" as I'm trying to cut down the > number of GUI based tools that I use because this box is _crawling_ along > with RH8.0. I want to be able to monitor how much of the file has > downloaded. When I configure up2date, there's a specific "StorageDir" > which is /var/spool/up2date. I'd like to do a "ls -lh /var/spool/up2date". up2date-nox normally displays the progress for me (at least on 7.3). I haven't gotten to upgrading my servers yet. Have you considered the possibility that up2date doesn't actually store it anywhere on disk until it's downloaded? > 2. Curiosity. I like to know where things are going and how they work. > And at this stage I'm upset that "lsof -c up2date" doesn't reveal where > the downloaded file is being stored. I find that deeply disturbing. Try 'strace up2date' and be prepared to look through a whole bunch of output. :-) PDG -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
