Menu
▾
▴
apt-proxy-users — Users of apt-proxy
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
(5) |
Mar
|
Apr
(2) |
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2002 |
Jan
(2) |
Feb
(5) |
Mar
(14) |
Apr
(1) |
May
(7) |
Jun
(2) |
Jul
(7) |
Aug
(13) |
Sep
(21) |
Oct
(3) |
Nov
|
Dec
|
| 2003 |
Jan
(6) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(5) |
Nov
|
Dec
(3) |
| 2004 |
Jan
(11) |
Feb
(2) |
Mar
(4) |
Apr
|
May
(9) |
Jun
|
Jul
(1) |
Aug
(12) |
Sep
(6) |
Oct
(7) |
Nov
(10) |
Dec
(3) |
| 2005 |
Jan
(22) |
Feb
(20) |
Mar
(5) |
Apr
(10) |
May
(15) |
Jun
(14) |
Jul
(9) |
Aug
(3) |
Sep
(7) |
Oct
(1) |
Nov
(3) |
Dec
(12) |
| 2006 |
Jan
(1) |
Feb
(1) |
Mar
(5) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(2) |
| 2007 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Larry M. <Lar...@Sp...> - 2004-08-21 22:57:42
|
Chris replied that apt-proxy-v2 is a standalone daemon that doesn't (yet) run
under inetd or xinetd. If you have this problem, it's easy to fix under xinetd
(even for noobs like me :)
* Move the apt-proxy service start-up file to a safe place (in anticipation of
xinetd support Real Soon Now), like so:
# mv /etc/xinetd.d/apt-proxy /usr/share/doc/apt-proxy # Or someplace
* Make sure apt-proxy is stopped, restart xinetd, then start apt-proxy:
# /etc/init.d/apt-proxy stop
Quoting Larry McCarthy <Lar...@Sp...>:
> Hi,
>
> Running a mixed Sid/Sarge system. Just installed apt-proxy-v2 (a.k.a. 1.9.17)
> from testing. Now the service won't restart under xinetd, complaining that
> 9999
> is already in use. I've tried restating both xinetd and apt-proxy, but the
> results are the same. netstat says nothing is using port 9999.
>
> It's probably something simple, but I'm an xinetd-noob, I'm afraid.
>
> tia for any help,
> Larry.
>
> /var/log/apt-proxy.log (Pls forgive the large inline):
>
> 2004/08/21 09:35 PDT [-] twistd 1.3.0rc1 (/usr/bin/python2.3 2.3.4) starting
> up
> 2004/08/21 09:35 PDT [-] reactor class:
> twisted.internet.default.SelectReactor
> 2004/08/21 09:35 PDT [-] Loading /usr/sbin/apt-proxy...
> 2004/08/21 09:35 PDT [-] Updating twisted's process module.
> 2004/08/21 09:35 PDT [-] No updating required.
> 2004/08/21 09:35 PDT [-] Loaded.
> 2004/08/21 09:35 PDT [-] apt_proxy.apt_proxy.Factory starting on 9999
> 2004/08/21 09:35 PDT [-] Traceback (most recent call last):
> 2004/08/21 09:35 PDT [-] File "/usr/bin/twistd2.3", line 36, in ?
> 2004/08/21 09:35 PDT [-] run()
> 2004/08/21 09:35 PDT [-] File
> "/usr/lib/python2.3/site-packages/twisted/scripts/twistd.py", line 184, in
> run
> 2004/08/21 09:35 PDT [-] app.run(runApp, ServerOptions)
> 2004/08/21 09:35 PDT [-] File
> "/usr/lib/python2.3/site-packages/twisted/application/app.py", line 205, in
> run
> 2004/08/21 09:35 PDT [-] runApp(config)
> 2004/08/21 09:35 PDT [-] File
> "/usr/lib/python2.3/site-packages/twisted/scripts/twistd.py", line 175, in
> runApp
> 2004/08/21 09:35 PDT [-] startApplication(config, application)
> 2004/08/21 09:35 PDT [-] File
> "/usr/lib/python2.3/site-packages/twisted/scripts/twistd.py", line 159, in
> startApplication
> 2004/08/21 09:35 PDT [-]
> service.IService(application).privilegedStartService()
> 2004/08/21 09:35 PDT [-] File
> "/usr/lib/python2.3/site-packages/twisted/application/service.py", line 205,
> in
> privilegedStart
> Service
> 2004/08/21 09:35 PDT [-] service.privilegedStartService()
> 2004/08/21 09:35 PDT [-] File
> "/usr/lib/python2.3/site-packages/twisted/application/internet.py", line 57,
> in
> privilegedStart
> Service
> 2004/08/21 09:35 PDT [-] self._port = self._getPort()
> 2004/08/21 09:35 PDT [-] File
> "/usr/lib/python2.3/site-packages/twisted/application/internet.py", line 74,
> in
> _getPort
> 2004/08/21 09:35 PDT [-] return getattr(reactor,
> 'listen'+self.method)(*self.args, **self.kwargs)
> 2004/08/21 09:35 PDT [-] File
> "/usr/lib/python2.3/site-packages/twisted/internet/default.py", line 283, in
> listenTCP
> 2004/08/21 09:35 PDT [-] p.startListening()
> 2004/08/21 09:35 PDT [-] File
> "/usr/lib/python2.3/site-packages/twisted/internet/tcp.py", line 594, in
> startListening
> 2004/08/21 09:35 PDT [-] raise CannotListenError, (self.interface,
> self.port, le)
> 2004/08/21 09:35 PDT [-] twisted.internet.error.CannotListenError: Couldn't
> listen on any:9999: (98, 'Address already in use').
>
> xinetd 2.3.13
>
> /var/log/daemon.log (snippet around xinet restart)
> [...snip...]
> Aug 21 09:35:33 ipanema xinetd[1914]: Exiting...
> Aug 21 09:35:33 ipanema xinetd[5706]: Reading included configuration file:
> /etc/xinetd.d/apt-proxy [file=/etc/xinetd.conf] [line=11]
> Aug 21 09:35:33 ipanema xinetd[5706]: Reading included configuration file:
> /etc/xinetd.d/chargen [file=/etc/xinetd.d/chargen] [line=11]
> [...snip...]
>
> /etc/xinetd.d/apt-proxy:
> service apt-proxy
> {
> disable = no
> socket_type = stream
> protocol = tcp
> port = 9999
> wait = no
> user = (*scrubbed*)
> server = /usr/sbin/apt-proxy
> server_args = /var/log/apt-proxy.log
> }
>
>
>
>
|
|
From: Larry M. <Lar...@Sp...> - 2004-08-21 18:37:12
|
Hi,
Running a mixed Sid/Sarge system. Just installed apt-proxy-v2 (a.k.a. 1.9.17)
from testing. Now the service won't restart under xinetd, complaining that 9999
is already in use. I've tried restating both xinetd and apt-proxy, but the
results are the same. netstat says nothing is using port 9999.
It's probably something simple, but I'm an xinetd-noob, I'm afraid.
tia for any help,
Larry.
/var/log/apt-proxy.log (Pls forgive the large inline):
2004/08/21 09:35 PDT [-] twistd 1.3.0rc1 (/usr/bin/python2.3 2.3.4) starting up
2004/08/21 09:35 PDT [-] reactor class: twisted.internet.default.SelectReactor
2004/08/21 09:35 PDT [-] Loading /usr/sbin/apt-proxy...
2004/08/21 09:35 PDT [-] Updating twisted's process module.
2004/08/21 09:35 PDT [-] No updating required.
2004/08/21 09:35 PDT [-] Loaded.
2004/08/21 09:35 PDT [-] apt_proxy.apt_proxy.Factory starting on 9999
2004/08/21 09:35 PDT [-] Traceback (most recent call last):
2004/08/21 09:35 PDT [-] File "/usr/bin/twistd2.3", line 36, in ?
2004/08/21 09:35 PDT [-] run()
2004/08/21 09:35 PDT [-] File
"/usr/lib/python2.3/site-packages/twisted/scripts/twistd.py", line 184, in run
2004/08/21 09:35 PDT [-] app.run(runApp, ServerOptions)
2004/08/21 09:35 PDT [-] File
"/usr/lib/python2.3/site-packages/twisted/application/app.py", line 205, in run
2004/08/21 09:35 PDT [-] runApp(config)
2004/08/21 09:35 PDT [-] File
"/usr/lib/python2.3/site-packages/twisted/scripts/twistd.py", line 175, in
runApp
2004/08/21 09:35 PDT [-] startApplication(config, application)
2004/08/21 09:35 PDT [-] File
"/usr/lib/python2.3/site-packages/twisted/scripts/twistd.py", line 159, in
startApplication
2004/08/21 09:35 PDT [-]
service.IService(application).privilegedStartService()
2004/08/21 09:35 PDT [-] File
"/usr/lib/python2.3/site-packages/twisted/application/service.py", line 205, in
privilegedStart
Service
2004/08/21 09:35 PDT [-] service.privilegedStartService()
2004/08/21 09:35 PDT [-] File
"/usr/lib/python2.3/site-packages/twisted/application/internet.py", line 57, in
privilegedStart
Service
2004/08/21 09:35 PDT [-] self._port = self._getPort()
2004/08/21 09:35 PDT [-] File
"/usr/lib/python2.3/site-packages/twisted/application/internet.py", line 74, in
_getPort
2004/08/21 09:35 PDT [-] return getattr(reactor,
'listen'+self.method)(*self.args, **self.kwargs)
2004/08/21 09:35 PDT [-] File
"/usr/lib/python2.3/site-packages/twisted/internet/default.py", line 283, in
listenTCP
2004/08/21 09:35 PDT [-] p.startListening()
2004/08/21 09:35 PDT [-] File
"/usr/lib/python2.3/site-packages/twisted/internet/tcp.py", line 594, in
startListening
2004/08/21 09:35 PDT [-] raise CannotListenError, (self.interface,
self.port, le)
2004/08/21 09:35 PDT [-] twisted.internet.error.CannotListenError: Couldn't
listen on any:9999: (98, 'Address already in use').
xinetd 2.3.13
/var/log/daemon.log (snippet around xinet restart)
[...snip...]
Aug 21 09:35:33 ipanema xinetd[1914]: Exiting...
Aug 21 09:35:33 ipanema xinetd[5706]: Reading included configuration file:
/etc/xinetd.d/apt-proxy [file=/etc/xinetd.conf] [line=11]
Aug 21 09:35:33 ipanema xinetd[5706]: Reading included configuration file:
/etc/xinetd.d/chargen [file=/etc/xinetd.d/chargen] [line=11]
[...snip...]
/etc/xinetd.d/apt-proxy:
service apt-proxy
{
disable = no
socket_type = stream
protocol = tcp
port = 9999
wait = no
user = (*scrubbed*)
server = /usr/sbin/apt-proxy
server_args = /var/log/apt-proxy.log
}
|
|
From: Marius L. L. <tr...@tr...> - 2004-07-10 19:25:20
|
apt-proxy-import 0.4 I get this error while I'm trying to import alot off debs. apt-proxy-import -d -D /usr/data/bullseye-305GB/apt-light Clearing temporary directory /var/cache/apt-proxy/dpkg-name.links /usr/data/bullseye-305GB/apt-light: Creating links with correct names with dpkg-name /usr/sbin/apt-proxy-import: /usr/bin/dpkg-name: /bin/sh: bad interpreter: Argument list too long Contents of /var/cache/apt-proxy/dpkg-name.links: total 0 Skipping * - unsupported type Anyone have a clue? -- Vennlig hilsen / Sincerely yours Marius Lund Larsen tr...@tr... http://www.trench.org |
|
From: micha <mic...@gm...> - 2004-05-25 22:36:51
|
(ap 1.3.6) Hi, what about this log entry: << [7133 17:51:06] Delivered partial file /var/cache/apt-proxy/debian/pool/main/n/netkit-ntalk/talkd_0.17-8_i386.deb, from offset 14156. dpkg: failed to open configuration file `/root/.dpkg.cfg' for reading: Permission denied >> I use to have /root with permissions rwxr-x---, owner root.staff Seems like i'm urged to make it rwxr-xr-x ? tia --mi. |
|
From: Chris H. <ha...@de...> - 2004-05-14 12:56:37
|
On Wed, 2004-05-12 at 17:28, Francesco P. Lovergine wrote: > On Wed, May 12, 2004 at 05:19:44PM +0200, Amaya wrote: > > Data has also showed interest in taking over some of his packages, I > > can't recall which one right now, as I am still a little "out of > > service", (whas it apt-proxy?), and as friends of him, we'd like to > > mantain his packages if it's fine with the rest of the DD. > Yes, that's also apt-proxy. It was co-maint when I checked on > packages.qa.debian.org. I don't know if chris changed mind > on maintaining. Current sid package has ranty as maintainer indeed. Current sid is still officially mine; ranty did the rewrite in experimental, and the plan was for him to take over once version 2 was ready for sid. But he wrote to me in January saying he wouldn't have any time for a while and it might be a good idea to look for someone with more time. In the meantime I implemented some more features and made some uploads, and I had already swapped Uploaders & Maintainer (in CVS but not yet uploaded) until ranty came back. I have enough work with openoffice, so I'd be glad if Data (or anyone else) was interested in helping out with apt-proxy. It's very close to going into sid now; it just needs a fix for the max_versions implementation. I was deeply shocked when I read about his death. We talked a lot via IRC and email, although I hadn't had the opportunity to meet him in person. I think it would be appropriate to dedicate version 2 to him. Chris |
|
From: Olivier B. <Oli...@pu...> - 2004-05-12 07:57:27
|
Hello,
In my last job, I was using apt-proxy v1 for our Debian network, and we
were very happy with it. It has only one problem: it was slow.
Now, in my new job, I have installed apt-proxy v2, and the speed is very
good. (note that we have a 100 MB Internet connection. :-D )
But there is a problem. Sometime, when I do the "apt-get update", I
have:
...
Hit http://aptproxy stable/main Packages
90% [Waiting for headers]
Err http://aptproxy stable/main Release
Connection failed
Hit http://aptproxy testing/main Packages
Err http://aptproxy testing/main Release
Connection failed
Err http://aptproxy unstable/main Packages
Connection failed
Err http://aptproxy unstable/main Release
Connection failed
Hit http://aptproxy idiap/misc Packages
Ign http://aptproxy idiap/misc Release
Failed to fetch http://aptproxy:9999/kde3/dists/stable/main/binary-i386=
/Packages.gz 404 Not Found
Failed to fetch http://aptproxy:9999/marillat/dists/stable/main/binary-=
i386/Release Connection failed
Failed to fetch http://aptproxy:9999/marillat/dists/testing/main/binary=
-i386/Release Connection failed
Failed to fetch http://aptproxy:9999/marillat/dists/unstable/main/binar=
y-i386/Packages.gz Connection failed
Failed to fetch http://aptproxy:9999/marillat/dists/unstable/main/binar=
y-i386/Release Connection failed
Reading Package Lists... Done
E: Some index files failed to download, they have been ignored, or old =
ones used instead.
The 404 Not Found is correct. But all the "Connection failed" are not
correct.
On the apt-proxy log file, I have found this information:
2004/05/12 08:54 CEST [FTPClient,client] --> 530 Sorry, only two connec=
tions per IP address are allowed
If I restart two or three times the apt-proxy server, then all is OK and
I can "apt-get update". But next day, the same problem come up. I
suspect that this is because apt-proxy do many ftp session at the same
time. The backend for marillat is:
backends =3D ftp://ftp.nerim.net/debian-marillat
Can I set that this backend must not runs many sessions at the same
time ?
Thanks in advance.
Olivier
--=20
Olivier Bornet | fran=E7ais : http://puck.ch/f
Swiss Ice Hockey Results | english : http://puck.ch/e
http://puck.ch/ | deutsch : http://puck.ch/g
Oli...@pu... | italiano : http://puck.ch/i
Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/
|
|
From: Chris H. <ha...@de...> - 2004-05-05 13:46:20
|
On Wed, 2004-05-05 at 14:52, Martijn Brouwer wrote: > E: Some index files failed to download, they have been ignored, or old > ones used instead. > > But it was much faster :) Do you have another suggestion? Oh :( No, sorry I'm not very familiar with dd. > About the python version: I do not want to mess up my server, so for the > time being I will not swith to apt-proxy v2. Hopefully, sarge will be > stable soon... I understand; although you could always set up a sarge chroot environment. It's reasonably easy, provided you have the disk space (um, around 200Mb I would guess) available. Assuming you use /chroot for the environment, replace MIRROR with your local debian mirror. This can be an apt-proxy (use HOSTNAME:9999): apt-get install debootstrap mkdir /chroot debootstrap sarge /chroot http://MIRROR/debian cp /etc/resolv.conf /chroot/etc/resolv.conf chroot /chroot echo 'deb http://MIRROR/debian sarge main' > /etc/apt/sources.list echo 'deb http://MIRROR/debian project/experimental/main/binary-$(ARCH)/' >> /etc/apt/sources.list apt-get update apt-get install apt-proxy/experimental Hope that helps, Chris |
|
From: Martijn B. <e.a...@tn...> - 2004-05-05 12:53:45
|
Chris Halls wrote: >Hi Martijn, >On Tue, 2004-05-04 at 00:16, Martijn Brouwer wrote: > > >>I am running apt-proxy (the old version) on an old computer with debian >>woody. I noticed that dd consumes all cpu, which makes total performance >>poor (throughput of 20kb/s instead of 75kb/s). This is due to the ibs=1 >>option. >> >> > >Oh, that's not good :( > >What happens if you try increasing the ibs and obs sizes to the length >of the message? I don't know if this might work: > > I tried the your suggestion, and when I ran apt-get update I got this output: Get:2 http://server sarge/main Packages 99% [2 Packages gzip 0] [Connecting to server (192.168.0.1)] 66.1kB/s 0s gzip: stdin: invalid compressed data--format violated Err http://server sarge/main Packages Sub-process gzip returned an error code (1) Get:3 http://server sarge/main Release [81B] Err http://server sarge/non-free Packages 0 OK Get:4 http://server sarge/non-free Release [85B] Err http://server sarge/contrib Packages 0 OK Get:5 http://server sarge/contrib Release Fetched 3579kB in 1m29s (39.9kB/s) Failed to fetch http://server:9999/debian/dists/sarge/main/binary-i386/Packages.gz Sub-process gzip returned an error code (1) Failed to fetch http://server:9999/debian/dists/sarge/non-free/binary-i386/Packages.gz 0 OK Failed to fetch http://server:9999/debian/dists/sarge/contrib/binary-i386/Packages.gz 0 OK Reading Package Lists... Done W: Couldn't stat source package list http://server sarge/main Packages (/var/lib/apt/lists/server:9999_debian_dists_sarge_main_binary-i386_Packages) - stat (2 No such file or directory) W: Couldn't stat source package list http://server sarge/main Packages (/var/lib/apt/lists/server:9999_debian_dists_sarge_main_binary-i386_Packages) - stat (2 No such file or directory) W: You may want to run apt-get update to correct these problems E: Some index files failed to download, they have been ignored, or old ones used instead. But it was much faster :) Do you have another suggestion? About the python version: I do not want to mess up my server, so for the time being I will not swith to apt-proxy v2. Hopefully, sarge will be stable soon... Thanks for your help Martijn |
|
From: Chris H. <ha...@de...> - 2004-05-04 09:54:18
|
Hi Martijn,
On Tue, 2004-05-04 at 00:16, Martijn Brouwer wrote:
> I am running apt-proxy (the old version) on an old computer with debian
> woody. I noticed that dd consumes all cpu, which makes total performance
> poor (throughput of 20kb/s instead of 75kb/s). This is due to the ibs=1
> option.
Oh, that's not good :(
What happens if you try increasing the ibs and obs sizes to the length
of the message? I don't know if this might work:
Change
dd ibs=1 obs=16384 skip=$2 count=$3 if="$1" 2>/dev/null
To
dd ibs=$(( $3 - $2 )) obs=$(( $3 - $2 )) skip=$2 count=$3 if="$1" 2>/dev/null
> Now I am considering using v2, but this one requires python 2.3
> according to the info in the deb from experimental. Can I run this one
> on woody with python 2.1?
The main problem is not with the Python version, it is with the
python-twisted version. Twisted wasn't really stable until around
version 0.99, and Woody only has 0.15 AFAIK.
I don't think apt-proxy has been tested with Python 2.1, and I don't
know if there are any changes between 2.1 and 2.3 that would cause
problems. You'd just have to try it and see what happens.
Chris
|
|
From: Martijn B. <e.a...@tn...> - 2004-05-03 22:18:07
|
Hi, I am running apt-proxy (the old version) on an old computer with debian woody. I noticed that dd consumes all cpu, which makes total performance poor (throughput of 20kb/s instead of 75kb/s). This is due to the ibs=1 option. Now I am considering using v2, but this one requires python 2.3 according to the info in the deb from experimental. Can I run this one on woody with python 2.1? Bye, Martijn Brouwer |
|
From: Olivier B. <Oli...@pu...> - 2004-05-01 17:38:58
|
Hi Micha, > Apt errors > E: Dynamic MMap ran out of room This is not a apt-proxy problem, but an apt-get error. You have too much lines in your sources.list file. To have a bigger "Dynamic MMap", one solutions is to add a file in /etc/apt/apt.conf.d (for example 80cachelimit) with the content: APT::Cache-Limit 12582912; (Adapt the number to what you want). For more help, search the web with google and your error message. You will find many answers. Good day. Olivier --=20 Olivier Bornet | fran=E7ais : http://puck.ch/f Swiss Ice Hockey Results | english : http://puck.ch/e http://puck.ch/ | deutsch : http://puck.ch/g Oli...@pu... | italiano : http://puck.ch/i Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/ |
|
From: micha <mic...@gm...> - 2004-05-01 17:24:12
|
I run ap version 1 from Debian stable, and now i try to upgrade to testing.
After 'updating' to the new sources list from aptitude ('u') the package lists
seem to have been downloaded
into the apt-proxy cache properly. For example:
<<
/home mi: ls -l /var/cache/apt-proxy/debian/dists/testing/main/binary-i386/
-rw-r--r-- 1 aptproxy nogroup 2,8M 2004-04-30 21:00 Packages.gz
-rw-r--r-- 1 aptproxy nogroup 81 2004-04-30 21:18 Release
>>
But when i start aptitude and it finishs loading the apt cache, there's this
error message:
<<
Apt errors
E: Dynamic MMap ran out of room
E: Error occured while processing tqsllib0 (NewVersion1)
E: Problem with MergeList
/var/lib/apt/lists/localhost:9999_debian_dists_testing_main_binary-i386_Packages
E: The package lists or status file could not be parsed or opened.
>>
There's no package list available, afterwards.
When i request a new (offline) upgrade, it says
<<
Ouch! Got SIGSEGV, dying..
Segmentation fault
>>
The same occurs with unstable.
Updating the package list still works for stable (woody).
The package lists for testing and unstable (main) are quite large (> 2,5 MB)
compared to stable.
However i don't understand what's going on.
This box has 256 MB RAM and a lot of swap. It runs a kernel 2.4.5 which never
showed any memory problem.
Any idea will be greatly appreciated !
-- mi.
------------------------------------- Appendix I: apt-proxy.conf
<<
# Change this path if you do not want to keep your cache under var
APT_PROXY_CACHE=/var/cache/apt-proxy
# ------------- Debian Main
# deb http://APTPROXY:9999/debian stable main contrib non-free
add_backend /debian/ \
$APT_PROXY_CACHE/debian/ \
http://ftp.de.debian.org/debian/ \
# ------------- Debian Non-US
add_backend /non-US/ \
$APT_PROXY_CACHE/non-US/ \
http://ftp.de.debian.org/debian-non-US/
# ------------- Debian Security
add_backend /security/ \
$APT_PROXY_CACHE/security/ \
http://security.debian.org/
# ------------- Openoffice: Backports to woody
add_backend /debian-openoffice/ \
$APT_PROXY_CACHE/debian-openoffice/ \
http://ftp.freenet.de/pub/debian-openoffice/
# ------------- GNOME-2.2: Backports to woody
add_backend /gnome/ \
$APT_PROXY_CACHE/gnome/ \
http://mirror.raw.no/
############################## OTHER VARS ##################################
# Automatically delete old debs when we download a newer one
# after this many days of the older not being accessed.
# Comment out to avoid, set to 0 for `instantly' (not recommended;
# sometimes the new versions are broken
CLEANUP_DAYS=14
# Once every n days, look through tree to erase any debs which
# haven't been accessed in that long (eg. obsolete, rarely used, etc).
# Comment out to disable.
# CLEAN_SWEEP=60
# Maximum number of versions of each package to keep in cache
# directory. Version purging is carried out immediately after a new
# version is downloaded.
# XXX Specific number for every package server
MAX_VERSIONS=3
# Maximum frequency of Packages/etc. updates from back end (minutes)
# Keep high to speed things up.
BACKEND_FREQ=240
# Number of seconds for rsync to wait before timing out.
RSYNC_TIMEOUT=20
# Number of seconds for wget to wait to connect before timing out.
WGET_TIMEOUT=20
# Uncomment to change the path to wget, or add extra options. For
# example, if you are behind a firewall that does not allow active
# FTP, use WGET="wget --passive-ftp"
#WGET=wget
# Uncomment to change the path to rsync or add extra options.
#RSYNC=rsync
# Uncomment to keep stats of successful backend transfers in the log.
#KEEP_STATS=1
# Uncomment this for debugging messages
# DEBUG=true
# HTTP/FTP proxy: apt-proxy uses wget to retreive files. Wget uses
# the http_proxy and ftp_proxy environment variables, which can be set
# like this:
#export http_proxy=http://proxy:8080/
#export ftp_proxy=http://proxy:8080/
>>
------------------------------------- Appendix II: etc/apt/sources.list
(here: pointing to testing)
# __________ EXPERIMENTAL:
#
# deb http://APTPROXY:9999/debian project/experimental/main/binary-$(ARCH)/
#
# __________ UNSTABLE:
#
#deb http://localhost:9999/debian unstable main contrib non-free
#deb http://localhost:9999/non-US unstable/non-US main contrib non-free
#
# __________ TESTING:
#
deb http://localhost:9999/debian testing main contrib non-free
deb http://localhost:9999/non-US testing/non-US main contrib non-free
#
# __________ STABLE:
#
#deb http://localhost:9999/debian stable main contrib non-free
#deb http://localhost:9999/non-US stable/non-US main contrib non-free
# security
#deb http://localhost:9999/security stable/updates main contrib non-free
## Openoffice Backports to woody
## deb http://localhost:9999/debian-openoffice woody main contrib
## Gnome-2.2 Backports to woody
## deb http://localhost:9999/gnome gnome2.2/
|
|
From: Gettert, W. <Wol...@fc...> - 2004-03-09 13:44:40
|
Hi Michael, thanks. No it was something else. The problem was in sources.list. For some reason which I don't know yet. apt-get has proplem with resolving tim (which is the name of the computer) but it can resolve tim.xxx.de. Even if I put the IP address of the computer into the sources.list it does not work. deb http://tim.xxx.de:9999/debian/ <---OK deb http://192.168.60.24:9999/debian/ <---- does not work deb http://tim:9999/debian/ <---- does not work Wolfram -----Original Message----- From: micha [mailto:mic...@gm...] Sent: Dienstag, 9. Marz 2004 12:51 Cc: apt...@li... Subject: Re: [Apt-proxy-users] 503 Service Unavailable etc/hosts.allow / deny ? example: lan0 (machines puck, piro only) and local (woody) /etc/hosts.allow: << apt-proxy: woody,piro.lan0,puck.lan0 /usr/sbin/apt-proxy -l /var/log/apt-proxy.log >> /etc/hosts.deny: << # All services will be denied for non-lan0 requests (except talk): ALL EXCEPT in.talkd: ALL EXCEPT piro.lan0,puck.lan0:DENY # secure: # ALL:DENY >> Gettert, Wolfram wrote: > tim:/etc/apt-proxy# apt-get update > Err http://tim stable/main Packages > 503 Service Unavailable > Ign http://tim stable/main Release > Err http://tim stable/non-free Packages > 503 Service Unavailable > Ign http://tim stable/non-free Release > Err http://tim stable/contrib Packages > 503 Service Unavailable > Ign http://tim stable/contrib Release > Failed to fetch > http://tim:9999/debian/dists/stable/main/binary-i386/Packages.gz 503 > Service Unavailable > Failed to fetch > http://tim:9999/debian/dists/stable/non-free/binary-i386/Packages.gz 503 > Service Unavailable > Failed to fetch > http://tim:9999/debian/dists/stable/contrib/binary-i386/Packages.gz 503 > Service Unavailable > Reading Package Lists... Done > W: Couldn't stat source package list http://tim stable/main Packages > (/var/lib/apt/lists/tim:9999_debian_dists_stable_main_binary-i386_Packages) > - stat (2 No such file or directory) > W: Couldn't stat source package list http://tim stable/non-free Packages > (/var/lib/apt/lists/tim:9999_debian_dists_stable_non-free_binary-i386_Packag > es) - stat (2 No such file or directory) > W: Couldn't stat source package list http://tim stable/contrib Packages > (/var/lib/apt/lists/tim:9999_debian_dists_stable_contrib_binary-i386_Package > s) - stat (2 No such file or directory) > W: You may want to run apt-get update to correct these problems > E: Some index files failed to download, they have been ignored, or old ones > used instead. > > > My /var/cache/apt-proxy.log is empty after this call of apt-get update. > > The permissions of the log file are OK. > -rw-r--r-- 1 aptproxy root 0 Mar 4 10:41 > /var/log/apt-proxy.log > > The permissions of /var/cache/apt-proxy are OK as well: > > tim:/etc/apt-proxy# ls -al /var/cache/apt-proxy/ > total 48 > drwxr-xr-x 5 aptproxy root 4096 Mar 3 15:08 . > drwxr-xr-x 9 root root 4096 Jan 29 08:45 .. > drwxr-xr-x 2 aptproxy nogroup 4096 Mar 3 11:04 debian > drwxr-xr-x 2 aptproxy nogroup 4096 Mar 3 11:04 non-US > drwxr-xr-x 2 aptproxy nogroup 4096 Mar 3 11:11 security > -rw-r--r-- 1 root root 24857 Mar 3 15:07 test > > > My /etc/apt/sources.list looks like this > deb http://tim:9999/debian/ stable main non-free contrib > > My /etc/inetd.conf looks contains this line > > ----------8<---- > 9999 stream tcp nowait.400 aptproxy /usr/sbin/tcpd > /usr/sbin/apt-proxy -l /var/log/apt-proxy.log > ----------8<---- > > My /etc/apt-proxy/apt-proxy.conf looks like this (please tell me if you want > to have > the complete file) > > ----------8<---- > add_backend /debian/ \ > $APT_PROXY_CACHE/debian/ \ > http://ftp.us.debian.org/debian/ \ > http://ftp.de.debian.org/debian/ \ > http://ftp.uk.debian.org/debian/ \ > ftp.us.debian.org::debian/ > ----------8<---- > > > I can successfully get the files with wget like this: > wget http://ftp.de.debian.org/debian/dists/stable/Release > > I can successfully connect to apt-proxy with > telnet tim 9999 > > I see all the things I type in the telnet session in > /var/log/apt-proxy.log > > But apt-get update still fails. Has anyone a good idea what I am > doing wrong. > > Thanks for any help. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Apt-proxy-users mailing list Apt...@li... https://lists.sourceforge.net/lists/listinfo/apt-proxy-users |
|
From: micha <mic...@gm...> - 2004-03-09 13:32:31
|
etc/hosts.allow / deny ? example: lan0 (machines puck, piro only) and local (woody) /etc/hosts.allow: << apt-proxy: woody,piro.lan0,puck.lan0 /usr/sbin/apt-proxy -l /var/log/apt-proxy.log >> /etc/hosts.deny: << # All services will be denied for non-lan0 requests (except talk): ALL EXCEPT in.talkd: ALL EXCEPT piro.lan0,puck.lan0:DENY # secure: # ALL:DENY >> Gettert, Wolfram wrote: > tim:/etc/apt-proxy# apt-get update > Err http://tim stable/main Packages > 503 Service Unavailable > Ign http://tim stable/main Release > Err http://tim stable/non-free Packages > 503 Service Unavailable > Ign http://tim stable/non-free Release > Err http://tim stable/contrib Packages > 503 Service Unavailable > Ign http://tim stable/contrib Release > Failed to fetch > http://tim:9999/debian/dists/stable/main/binary-i386/Packages.gz 503 > Service Unavailable > Failed to fetch > http://tim:9999/debian/dists/stable/non-free/binary-i386/Packages.gz 503 > Service Unavailable > Failed to fetch > http://tim:9999/debian/dists/stable/contrib/binary-i386/Packages.gz 503 > Service Unavailable > Reading Package Lists... Done > W: Couldn't stat source package list http://tim stable/main Packages > (/var/lib/apt/lists/tim:9999_debian_dists_stable_main_binary-i386_Packages) > - stat (2 No such file or directory) > W: Couldn't stat source package list http://tim stable/non-free Packages > (/var/lib/apt/lists/tim:9999_debian_dists_stable_non-free_binary-i386_Packag > es) - stat (2 No such file or directory) > W: Couldn't stat source package list http://tim stable/contrib Packages > (/var/lib/apt/lists/tim:9999_debian_dists_stable_contrib_binary-i386_Package > s) - stat (2 No such file or directory) > W: You may want to run apt-get update to correct these problems > E: Some index files failed to download, they have been ignored, or old ones > used instead. > > > My /var/cache/apt-proxy.log is empty after this call of apt-get update. > > The permissions of the log file are OK. > -rw-r--r-- 1 aptproxy root 0 Mar 4 10:41 > /var/log/apt-proxy.log > > The permissions of /var/cache/apt-proxy are OK as well: > > tim:/etc/apt-proxy# ls -al /var/cache/apt-proxy/ > total 48 > drwxr-xr-x 5 aptproxy root 4096 Mar 3 15:08 . > drwxr-xr-x 9 root root 4096 Jan 29 08:45 .. > drwxr-xr-x 2 aptproxy nogroup 4096 Mar 3 11:04 debian > drwxr-xr-x 2 aptproxy nogroup 4096 Mar 3 11:04 non-US > drwxr-xr-x 2 aptproxy nogroup 4096 Mar 3 11:11 security > -rw-r--r-- 1 root root 24857 Mar 3 15:07 test > > > My /etc/apt/sources.list looks like this > deb http://tim:9999/debian/ stable main non-free contrib > > My /etc/inetd.conf looks contains this line > > ----------8<---- > 9999 stream tcp nowait.400 aptproxy /usr/sbin/tcpd > /usr/sbin/apt-proxy -l /var/log/apt-proxy.log > ----------8<---- > > My /etc/apt-proxy/apt-proxy.conf looks like this (please tell me if you want > to have > the complete file) > > ----------8<---- > add_backend /debian/ \ > $APT_PROXY_CACHE/debian/ \ > http://ftp.us.debian.org/debian/ \ > http://ftp.de.debian.org/debian/ \ > http://ftp.uk.debian.org/debian/ \ > ftp.us.debian.org::debian/ > ----------8<---- > > > I can successfully get the files with wget like this: > wget http://ftp.de.debian.org/debian/dists/stable/Release > > I can successfully connect to apt-proxy with > telnet tim 9999 > > I see all the things I type in the telnet session in > /var/log/apt-proxy.log > > But apt-get update still fails. Has anyone a good idea what I am > doing wrong. > > Thanks for any help. |
|
From: Gettert, W. <Wol...@fc...> - 2004-03-04 09:59:12
|
Hi,
I try to run apt-proxy in our company. I was successfully at home with the
same
configuration file (apt-proxy.conf). I use apt-proxy 1.3.6.
When I try to run apt-get update on the local machine I get:
tim:/etc/apt-proxy# apt-get update
Err http://tim stable/main Packages
503 Service Unavailable
Ign http://tim stable/main Release
Err http://tim stable/non-free Packages
503 Service Unavailable
Ign http://tim stable/non-free Release
Err http://tim stable/contrib Packages
503 Service Unavailable
Ign http://tim stable/contrib Release
Failed to fetch
http://tim:9999/debian/dists/stable/main/binary-i386/Packages.gz 503
Service Unavailable
Failed to fetch
http://tim:9999/debian/dists/stable/non-free/binary-i386/Packages.gz 503
Service Unavailable
Failed to fetch
http://tim:9999/debian/dists/stable/contrib/binary-i386/Packages.gz 503
Service Unavailable
Reading Package Lists... Done
W: Couldn't stat source package list http://tim stable/main Packages
(/var/lib/apt/lists/tim:9999_debian_dists_stable_main_binary-i386_Packages)
- stat (2 No such file or directory)
W: Couldn't stat source package list http://tim stable/non-free Packages
(/var/lib/apt/lists/tim:9999_debian_dists_stable_non-free_binary-i386_Packag
es) - stat (2 No such file or directory)
W: Couldn't stat source package list http://tim stable/contrib Packages
(/var/lib/apt/lists/tim:9999_debian_dists_stable_contrib_binary-i386_Package
s) - stat (2 No such file or directory)
W: You may want to run apt-get update to correct these problems
E: Some index files failed to download, they have been ignored, or old ones
used instead.
My /var/cache/apt-proxy.log is empty after this call of apt-get update.
The permissions of the log file are OK.
-rw-r--r-- 1 aptproxy root 0 Mar 4 10:41
/var/log/apt-proxy.log
The permissions of /var/cache/apt-proxy are OK as well:
tim:/etc/apt-proxy# ls -al /var/cache/apt-proxy/
total 48
drwxr-xr-x 5 aptproxy root 4096 Mar 3 15:08 .
drwxr-xr-x 9 root root 4096 Jan 29 08:45 ..
drwxr-xr-x 2 aptproxy nogroup 4096 Mar 3 11:04 debian
drwxr-xr-x 2 aptproxy nogroup 4096 Mar 3 11:04 non-US
drwxr-xr-x 2 aptproxy nogroup 4096 Mar 3 11:11 security
-rw-r--r-- 1 root root 24857 Mar 3 15:07 test
My /etc/apt/sources.list looks like this
deb http://tim:9999/debian/ stable main non-free contrib
My /etc/inetd.conf looks contains this line
----------8<----
9999 stream tcp nowait.400 aptproxy /usr/sbin/tcpd
/usr/sbin/apt-proxy -l /var/log/apt-proxy.log
----------8<----
My /etc/apt-proxy/apt-proxy.conf looks like this (please tell me if you want
to have
the complete file)
----------8<----
add_backend /debian/ \
$APT_PROXY_CACHE/debian/ \
http://ftp.us.debian.org/debian/ \
http://ftp.de.debian.org/debian/ \
http://ftp.uk.debian.org/debian/ \
ftp.us.debian.org::debian/
----------8<----
I can successfully get the files with wget like this:
wget http://ftp.de.debian.org/debian/dists/stable/Release
I can successfully connect to apt-proxy with
telnet tim 9999
I see all the things I type in the telnet session in
/var/log/apt-proxy.log
But apt-get update still fails. Has anyone a good idea what I am
doing wrong.
Thanks for any help.
Wolfram
|
|
From: micha <mic...@gm...> - 2004-03-04 04:49:35
|
Hello, Beneath the original network application, ap also is quite useful for updating roaming machines from a base station. i feed now regularily several Laptops from an ap-server, and it works great. Thanks to the developers ! I'd wish ap could load packages without actually have to pass them somewhere for installation....i could do the requests (and maybe even investigate dependencies) altogether at the evening, and next morning going to suck the stuff to the other machines. I'm used to aptitude; so i would be happy to manage the apt-proxy cache directly with a kind of (modified) aptitude, doing orders and lookup dependencies. This would only show (from) where they are available, of course. Just the GUI, rather simple. Somehow this would demonstrate ap could become a basic element of the apt system one day. And the GUI could become part of aptitude. But my thoughts are running away. Again, it's quite good as it is. -- mi. |
|
From: Thorsten G. <tgu...@tg...> - 2004-02-14 00:37:52
|
On [Fri, 13.02.2004 17:41], Keith Edmunds wrote: > What I'm trying to do: install Samba V3 from www.backports.org whilst > otherwise maintaining a Woody system. > What works: without using apt-proxy, I can do this by adding the > following to sources.list: [snip] > Now, rather than pull those packages over the net each time, I want my > apt-proxy server to serve them. However, I'm not sure how to set it up > such that I can specify only the packages above are to come from > backports; the rest are to come from stable mirrors. The problem is that > once I add the appropriate lines to /etc/apt-proxy/apt-proxy.conf, the > 'origin' of the packages (as seen by 'apt-cache policy') is the local > apt-proxy server, and thus I cannot distinguish the backports packages > from the others. > Does that make sense? > Can what I want to do be done with apt-proxy? Yes, please check the backports archive (if there are any) and wait until Norbert finds time to add Release files (this will solve your problem). > Keith Thorsten -- There's a door Where does it go? It stays where it is, I think. (Terry Pratchett, Eric) |
|
From: Keith E. <ke...@mi...> - 2004-02-13 17:43:53
|
What I'm trying to do: install Samba V3 from www.backports.org whilst otherwise maintaining a Woody system. What works: without using apt-proxy, I can do this by adding the following to sources.list: deb http://www.backports.org/debian stable samba ...and having a /etc/apt/preferences like this: ==================================================== Package: * Pin: release a=stable Pin-Priority: 900 Package: samba Pin: origin www.backports.org Pin-Priority: 950 Package: samba-common Pin: origin www.backports.org Pin-Priority: 950 Package: libacl1 Pin: origin www.backports.org Pin-Priority: 950 Package: libattr1 Pin: origin www.backports.org Pin-Priority: 950 Explanation: Uninstall or do not install any Debian-originated Explanation: instances other than those in the stable distro Package: * Pin: release o=Debian Pin-Priority: -10 ==================================================== Now, rather than pull those packages over the net each time, I want my apt-proxy server to serve them. However, I'm not sure how to set it up such that I can specify only the packages above are to come from backports; the rest are to come from stable mirrors. The problem is that once I add the appropriate lines to /etc/apt-proxy/apt-proxy.conf, the 'origin' of the packages (as seen by 'apt-cache policy') is the local apt-proxy server, and thus I cannot distinguish the backports packages from the others. Does that make sense? Can what I want to do be done with apt-proxy? Keith |
|
From: mi <mic...@gm...> - 2004-01-27 08:58:02
|
Chris Halls wrote: > No, you should be able to run the older and the newer version using the > same cache. It adds some extra database files, but these are ignored by > version 1. that's good to hear. > twisted >=1.0 upgrading is no minor task for me. but it should be done someday anyway. thank you for reply -- mi. |
|
From: mi <mic...@gm...> - 2004-01-26 18:51:31
|
Chris Halls wrote: > Let me try again. > You _need_ a 'Packages' file to rsync with the backend. > You _need_ a 'Packages.gz' file to send to clients that request it. ok, that's clear now. >>What backend do you mean ? > Whichever backend you were talking about in the first place. I am sorry. It's the terminology which is new for me. I'm still learning english. I thought of some database management program on a package server. So i guess a backend is called the server a-p requests itself the packages from, in this case. And a-p subproceesses are called 'slaves'. ok ! What about a-p 2 ? Can i install it ? -- mi. |
|
From: Chris H. <ha...@de...> - 2004-01-26 08:55:32
|
On Wed, 2004-01-21 at 04:42, mi wrote: > Chris Halls wrote: > > If you are using an rsync backend, it is more efficient to rsync > > 'Packages', so it does that, and then uses gzip to make a Packages.gz t= o > > send to clients. > ok. It would be nicer though, to have no reminents. Not only a=20 > question of style. > I discovered some problems with relicts on standard office apps in the=20 > past. > At least, debugging becomes easier without them... Let me try again. You _need_ a 'Packages' file to rsync with the backend. You _need_ a 'Packages.gz' file to send to clients that request it. If you delete one of them you have to waste CPU recreating it later and apt-proxy becomes even slower than it already is. It's a CPU/disk space tradeoff and since this is supposed to be a package cache, you are more likely have a few MB disk space to spare than CPU cycles to waste. > > It's not a big problem - a Release file contains extra information abou= t > > a backend but is not essential. a-p cache's the fact that the Release > > file does not exist so it does not have to try the backend too > > frequently. > What backend do you mean ? Whichever backend you were talking about in the first place. > In debian main it says for my system: Great, now it is available. At the time the Release.fail was created, it was not reachable for whatever reason. > >>>If you're just starting out with apt-proxy, you might want to try the > >>>python rewrite, which is available from experimental and is much quick= er > >>>than v1. > I would like to. v1 seems to be significant slower than pure apt here.=20 > Approx. =F8 4 K instead of 5,5. > It's obvious when i download a large package. So it's probably not the=20 > rsync thing slowing it down ? You will get better throughput if you don't use the rsync protocol.=20 Actually, apt-proxy is the most efficient for large packages normally, since it just lets the slave program (wget or rsync) transfer the file from the internet to disk, and forwards it on to the clients. > But what's the difference. I use the same packet sources as before, of=20 > course. > However, i cannot install the recommended 'stat' package. You only need to worry about 'stat' on a plain woody system - it is part of later versions of the coreutils package. > >>I don't want to ditch woody/stable, hopefully a-p-2 runs under woody=20 > >>as well ? > > Oh, it needs twisted, which was not available in Woody, so no you can't > > use it I'm afraid. > I just have found and installed twisted 0.15.5-1 on a 3.0r1 CD. > It also installed the by now missing: > python-tk 2.1.3-3.2 > blt 2.4u-7 > blt-common 2.4u-7 > tix41 4.1.0.7-4.1 > Do you think this is sufficient to run ap2 ? I'm afraid twisted had too many bugs until about version 0.99, so you need to satisfy the dependency of twisted >=3D 1.0.0, which is very difficult on Woody. > And if so, where would i download it ? The same as all other experimental packages. You can find it by going to http://packages.debian.org/apt-proxy and choosing the experimental version. > I've no experience with cvs. I couldn't find any version 2.x -- or=20 > maybe it's still 1.x ? It is numbered 1.9.7 since 2.0 will be the first official stable release. > I found a tarball in a cvs branch. No version number. I think it=20 > wasn't the right one. > The config template is full of rsync. And the README says: > >> > Sat Dec 8 23:37:40 CET 2001 > Jan-Benedict Glaw <jb...@lu...> > << > He says he started ap2. I remember some people mentioned in the docs=20 > so far, > Rusty Russel, Manuel Estrada Sainz, Chris Halls. > But why isn't JB Glaw mentioned on the apt-proxy website ? That is not directly related to apt-proxy. He started a rewrite a long time ago but it did not get very far feature wise and I think he might have abandoned it. > I also became unsure about the official name. Is it 'apt-proxy' or=20 > 'ap2' or 'HEAD' ? It is version 2 of apt-proxy, which Manuel & I often abreviate to ap2.=20 It isn't in CVS HEAD at the moment - that is still version 1. > > ap2 does have upgrade scripts and should automatically update for you, > > but it needs more testing. > Does it change the cache structure ? No, you should be able to run the older and the newer version using the same cache. It adds some extra database files, but these are ignored by version 1. Chris |
|
From: Keith E. <ke...@mi...> - 2004-01-25 20:16:56
|
On Sun, 25 Jan 2004 20:08:22 +0000 Keith Edmunds <ke...@mi...> wrote: > I've spent the last couple of hours trying to set up apt-proxy(which > I've never done before), and I _know_ I've done something silly but I > can't work out what. I was right: I had done something silly. I had a proxy set in /etc/apt/apt.conf Sorry for wasting time and bandwidth. Keith |
|
From: Keith E. <ke...@mi...> - 2004-01-25 20:08:25
|
I've spent the last couple of hours trying to set up apt-proxy(which I've never done before), and I _know_ I've done something silly but I can't work out what. The error I get: # apt-get update Err http://localhost stable/main Packages 503 Service Unavailable Ign http://localhost stable/main Release Err http://localhost stable/non-free Packages 503 Service Unavailable ...and so on... I can telnet to port 9999 OK, so it isn't an access problem. /etc/apt/sources.list: deb http://localhost:9999/main stable main non-free contrib deb-src http://localhost:9999/main stable main non-free contrib deb http://localhost:9999/non-US stable/non-US main contrib non-free deb-src http://localhost:9999/non-US stable/non-US main contrib non-free deb http://localhost:9999/security stable/updates main contrib non-free deb-src http://localhost:9999/security stable/updates main contrib non-free /etc/apt-proxy/apt-proxy.conf: APT_PROXY_CACHE=/var/cache/apt-proxy add_backend /main/ \ $APT_PROXY_CACHE/debian/ \ http://ftp.uk.debian.org/debian/ \ http://ftp.us.debian.org/debian/ \ http://ftp.de.debian.org/debian/ \ http://ftp2.de.debian.org/debian/ add_backend /non-US/ \ $APT_PROXY_CACHE/non-US/ \ http://ftp.uk.debian.org/debian/non-US/ \ http://ftp.de.debian.org/debian-non-US/ \ http://ftp2.de.debian.org/debian-non-US/ add_backend /security/ \ $APT_PROXY_CACHE/security/ \ http://security.debian.org/debian-security/ \ http://non-us.debian.org/debian-security/ CLEANUP_DAYS=30 MAX_VERSIONS=2 BACKEND_FREQ=240 RSYNC_TIMEOUT=30 WGET_TIMEOUT=30 KEEP_STATS=1 DEBUG=true Thanks, Keith |
|
From: mi <mic...@gm...> - 2004-01-23 04:15:49
|
Hello,
Recently i moved to xinetd, and i'm now wondering how a-p handles its
requests.
Does it multithreading ? Will there be new processes launched by inetd
for every request of one client ?
How about multiple requests by different clients ?
And how to set up xinetd correctly...
This is the default inetd.conf entry for ap, set by debian debconf:
<<
9999 stream tcp nowait.400 aptproxy /usr/sbin/tcpd
/usr/sbin/apt-proxy -l /var/log/apt-proxy.log
>>
The conversion script 'xconv.pl' didn't know how to 'translate' the
inetd.conf <nowait.max> entry.
In the documentation, i found the following xinetd.conf options:
<<
instances: The maximum number of requests a particular service may
handle at once.
per_source: The maximum number of connections a specific IP address
can have to a specific service.
>>
It's not matching exactly, but, anyway:
What would be the appropriate values for, say, 10 clients ?
This is what i set up so far in xinetd.conf:
<<
service 9999
{
disable = no
port = 9999
socket_type = stream
protocol = tcp
wait = no
instances = 50
per_source = 10
user = aptproxy
server = /usr/sbin/apt-proxy
server_args = -l /var/log/apt-proxy.log
}
>>
And, serving a LAN with 100 clients, should a-p better run as
standalone daemon there ?
Also, while there already are 82 services added for the debian
distribution, i wonder why debconf didn't add
an entry to /etc/services ?
Another question is how important would you consider it to invoke ap
though tcpd (say, on a production machine) ?
Though i didn't test it until now, I guess xinetd.conf then should read
<<
flags = NAMEINARGS
server = /usr/sbin/tcpd
server_args = /usr/sbin/apt-proxy -l /var/log/apt-proxy.log
>>
What do you think =)
--
mi.
|
|
From: mi <mic...@gm...> - 2004-01-21 03:42:17
|
Chris Halls wrote: > That's odd. The code only leaves the directory if the DEBUG variable is > set: > # remove directory if not debugging > [ -z "$DEBUG" ] && rm -rf "$APT_PROXY_CACHE/dpkg-name.links/" I do much configurating these days, andI can't remember every detail. Maybe i made it 'DEBUG=false' instead of unsetting it correctly. I am not sure. > If you are using an rsync backend, it is more efficient to rsync > 'Packages', so it does that, and then uses gzip to make a Packages.gz to > send to clients. ok. It would be nicer though, to have no reminents. Not only a question of style. I discovered some problems with relicts on standard office apps in the past. At least, debugging becomes easier without them... > It's not a big problem - a Release file contains extra information about > a backend but is not essential. a-p cache's the fact that the Release > file does not exist so it does not have to try the backend too > frequently. What backend do you mean ? In debian main it says for my system: >> Archive: stable Version: 3.0r2 Component: main Origin: Debian Label: Debian Architecture: i386 << >>>If you're just starting out with apt-proxy, you might want to try the >>>python rewrite, which is available from experimental and is much quicker >>>than v1. I would like to. v1 seems to be significant slower than pure apt here. Approx. ø 4 K instead of 5,5. It's obvious when i download a large package. So it's probably not the rsync thing slowing it down ? But what's the difference. I use the same packet sources as before, of course. However, i cannot install the recommended 'stat' package. It breaks coreutils, which is left from a little excursion to sarge last year. Don't ask me how it is possible to have debianutils and coreutils installed the same time. It makes doing anything on either of both packages impossible, because they altogether include some same files, and both are essential, so won't remove the other. I'm clueless at the moment. >>I don't want to ditch woody/stable, hopefully a-p-2 runs under woody >>as well ? > Oh, it needs twisted, which was not available in Woody, so no you can't > use it I'm afraid. I just have found and installed twisted 0.15.5-1 on a 3.0r1 CD. It also installed the by now missing: python-tk 2.1.3-3.2 blt 2.4u-7 blt-common 2.4u-7 tix41 4.1.0.7-4.1 Do you think this is sufficient to run ap2 ? And if so, where would i download it ? I've no experience with cvs. I couldn't find any version 2.x -- or maybe it's still 1.x ? I found a tarball in a cvs branch. No version number. I think it wasn't the right one. The config template is full of rsync. And the README says: >> Sat Dec 8 23:37:40 CET 2001 Jan-Benedict Glaw <jb...@lu...> << He says he started ap2. I remember some people mentioned in the docs so far, Rusty Russel, Manuel Estrada Sainz, Chris Halls. But why isn't JB Glaw mentioned on the apt-proxy website ? No it's definteley very old. Can you give me the right URL ? I also became unsure about the official name. Is it 'apt-proxy' or 'ap2' or 'HEAD' ? Perhaps you can help me clear my 'personal cache' here ;-) > ap2 does have upgrade scripts and should automatically update for you, > but it needs more testing. Does it change the cache structure ? -- mi. |
