Re: [Apt-proxy-users] cache cleaning: deleting obsolete files

[Chris H. <ha...@de...>]

On Thursday 23 March 2006 03:55, Micha wrote:
> | Your configuration as shown should work... but only if a-p has been
> | running for a whole day. Try setting cleanup_freq to something small so
> | the cleanup cycle is started quickly, e.g. 30m.
>
> Hey, wait ! Looks like i misinterpreted it.
> I thought it would check the date...but it checks uptime ?
> That would explain a lot. I shutdown the box every day.
> I just thought the cleanup didn't work correctly, somehow.

It's a bug. See this report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343922

> Hmmm...i still would prefer to run the cleanup only on demand,
> i do compiling/installing more often, and the ap background process could
> slow down things when i like to have 100% cpu myself...

The cleanup does a lot of sleeping in between each disk access so that it does 
not disturb any busy processes. It should use less than 0.5% CPU, depending 
on your processor speed.

> There's no commandline to trigger cleanup, right?

No, but it sounds like it might be a good idea to add this.

> Perhaps simply restart then with cleanup_freq = 1m...However:
> Tried it right now, but i can't see any twisted process activity,
> nor anything in the ap log ?

That's strange. I see activity on my version, although I am working on a 
different version of the code.

> How about telnet, connecting to the running server ?

It should be possible, but I can't get this working properly either - maybe it 
is because of the deprecated error that you saw.

It is probably best for you to use find to remove the files for now, until bug 
#343922 is fixed.

> I just enabled the config options for port 998 and restarted ap and tried a
> simple telnet connect but i can't get any connection there, 

It will only enable the telnet server if you specify a port, username and 
password. Maybe something was not spelled correctly.

> it seems to 
> work however on the normal http server port 9999. (without password
> request...?)

That is the HTTP socket. You can't do telnet commands to this port, only 
requests for files.

> I also dug holes into xinetd / libwrap / ident so they should be ok with
> telnet queries. libwrap (hosts.allow) is open for "apt-proxy:" and there's
> anyway no port assigned enywhere (in /etc/services) ....
> so why not 9998 ? Is there a mistake ?

Have a look at the debug log. It should say if it is listening. My version 
says:

2006/03/01 10:31 GMT [-] twisted.manhole.telnet.ShellFactory starting on 2222
2006/03/01 10:31 GMT [-] Starting factory <twisted.manhole.telnet.ShellFactory 
instance at 0xb77611ec>

(my telnet socket is port 2222)

> At this occasion i noticed that AP keeps a direct stream even if it can't
> use the cache anymore. Well done.

Erm, that is just a lucky accident :)

Chris