Update of /cvsroot/popfile/engine/Proxy
In directory sc8-pr-cvs1:/tmp/cvs-serv11068/Proxy
Modified Files:
POP3.pm
Log Message:
Improved the handling of failure to open the POP3 or HTTP ports by writing out a comprehensive error message explaining the situation
Index: POP3.pm
===================================================================
RCS file: /cvsroot/popfile/engine/Proxy/POP3.pm,v
retrieving revision 1.36
retrieving revision 1.37
diff -C2 -d -r1.36 -r1.37
*** POP3.pm 18 Feb 2003 14:46:33 -0000 1.36
--- POP3.pm 21 Feb 2003 18:22:02 -0000 1.37
***************
*** 132,136 ****
LocalPort => $self->{configuration}->{configuration}{port},
Listen => SOMAXCONN,
! Reuse => 1 ) or return 0;
# This is used to perform select calls on the $server socket so that we can decide when there is
--- 132,150 ----
LocalPort => $self->{configuration}->{configuration}{port},
Listen => SOMAXCONN,
! Reuse => 1 );
!
! if ( !defined( $self->{server} ) ) {
! print <<EOM;
!
! \nCouldn't start the POP3 proxy because POPFile could not bind to the
! POP3 listen port $self->{configuration}->{configuration}{port}. This could be because there is another service
! using that port or because you do not have the right privileges on
! your system (On Unix systems this can happen if you are not root
! and the port you specified is less than 1024).
!
! EOM
!
! return 0;
! }
# This is used to perform select calls on the $server socket so that we can decide when there is
***************
*** 210,214 ****
} else {
! # This is here so that we get in errorneous position where the pipready
# function is returning that there's data, but there is none, in fact the
# pipe is dead then we break the cycle here. This was happening to me when
--- 224,228 ----
} else {
! # This is here so that we get in errorneous position where the pipeready
# function is returning that there's data, but there is none, in fact the
# pipe is dead then we break the cycle here. This was happening to me when
|
