At 10:21 AM -0500 5/16/01, Wilson Machasilla wrote:
> All options works fine: -r -S -f /etc/config.apopper, etc. But the
> option -T don�t work!
I've not heard of this failing before. Try enabling debug tracing
and see what is going on. The debug trace records written by Qpopper
include the time, so you can see if the timeout is exceeded.
To enable tracing in Qpopper:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t tracefile'.
4. Send inetd a HUP signal.
This causes detailed tracing to be written to the syslog (if you used
'-d') or to the file specified as 'tracefile'.
Qpopper simply sets an alarm for the timeout when it is ready for
client input. So you may want to use truss(1), strace(1), or
whatever the system call trace facility is on your platform. That
will show if the alarm is being set, and if the signal is being sent.
