Some thoughts please..,
So after pains of my brothers hardware failing, an reinstall from
redhat to debian woody, restore from backups/mirrors
apt-proxy was installed and working fine, a few days
later ..
He installed swat (and maybe some other things, not sure)
and xinetd stopped listening for apt-proxy connections
on it's port 9999
restarting xinetd did not get it listening on port 9999
netstat -an | grep 9999 ** nothing
so.. I checked the config /etc/xinetd.conf and of course
it was in there,
so I stopped xinetd
/etc/init.d/xinetd stop
and started it up in debug mode
/usr/sbin/xinetd -reuse -d
and it shows what services it listens on, nothing about apt-proxy
and no error messages or anything,
so ...
went back to /etc/xinetd.conf and saw apt-proxy service definition
was straight port (like service 9999 { ... blah ... } )
but all the others weren't (time, identd, swat and 2 discards)
so I added an entry to /etc/services
apt-proxy 9999/tcp
and then changed the service definition to match
service apt-proxy { ... blah ... }
and restarted xinetd and it was listening again.
odd. Any ideas on why xinetd decided not to fire up on the port
when it wasn't in the services list ?
and what could have broken it in the first place .. ?
ramon.
--
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
