Hi On Wednesday 13 February 2008 08:13, Eric Cooper wrote: > On Wed, Feb 13, 2008 at 01:20:52AM +1100, Andrew Vaughan wrote: > > As the following sequence shows, approx failed to give an error > > message, (and appeared to start) even though port 9999 was already in > > use. (apt-cacher-ng was configured to use port 9999) > > Actually, it should have logged an error message. (Please check > /var/log/daemon.log or syslog to confirm that.) But the daemon has > already backgrounded itself at that point, so the /etc/init.d script > can't tell that it has exited.
Yeah there are errors messages in both daemon.log and syslog. > > I'll look into how hard it would be to bind the port sooner in the > startup sequence. A quick test show that errors in approx.conf (eg $interface aaa) can show the same symptoms (appears to start ok, but actually fails to start, errors messages in daemon.log and syslog). It might be worth seeing if its possible to parse and validate approx.conf before detaching. (Actually you'll have to do that for at least port and interface in any case). Thanks Andrew V. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
