apt-cacher-cleanup.pl loops when .conf has user=root
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt-cacher (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Binary package hint: apt-cacher
Was finding that apt-cacher-
Did went to /usr/share/
skip@
Simulation mode. Just printing what would be done.
Could not enter the cache dir at ./apt-cacher-
Did this and looped:
skip@
Simulation mode. Just printing what would be done.
Invoked as root, changing to root:root and re-execing.
Simulation mode. Just printing what would be done.
Invoked as root, changing to root:root and re-execing.
Simulation mode. Just printing what would be done.
Invoked as root, changing to root:root and re-execing.
Simulation mode. Just printing what would be done.
Invoked as root, changing to root:root and re-execing.
I don't know perl but I think it might be this code:
# change uid and gid if root
if ($cfg->{user} && !$> or $cfg->{group} && !$)) {
printmsg(
setup_
# Rexec to ensure /proc/self/fd ownerships correct which are needed for red
# patching with pdiffs
exec($0, @savedARGV) or die "Unable to rexec $0: $!\n";
}
I'm ASSUMING that $cfg is getting info from /etc/apt-
group=root
user=root
Can anyone explain when or why this was added? U believe my apt-cacher.conf has been coded like this since April of 2008 when I first installed it. The machine was recently (a couple months ago) upgraded from v8.04LTS to v10.04LTS of Xubuntu.
Running now with the "if" code above commented out and with the -s switch. It did GETs on the lists and now is "READING" all the repositories... wow, I've accumulated mucho 'stuff' in 2 years. Might consider just clearing out the cache and starting fresh.
Anyway, if anybody can tell me how I should be addressing this I'd love to hear. Thanx, Skip
Xubuntu v10.04
.......
skip@crunch20:~$ uname -a
Linux crunch20 2.6.32-24-generic #38-Ubuntu SMP Mon Jul 5 09:20:59 UTC 2010 x86_64 GNU/Linux
.......
skip@crunch20:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid
.......
skip@crunch20:~$ apt-cache policy apt-cacher
apt-cacher:
Installed: 1.6.10ubuntu2
Candidate: 1.6.10ubuntu2
Version table:
*** 1.6.10ubuntu2 0
500 http://
100 /var/lib/
.......
what I expected -> it to run in a timely manor (hour or two, not days)
what happened -> it ran for days
Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!