RE: too many popper processes

2001-01-15 Thread Alan Brown

> The folks at Qualcomm seem comatose about picking up and adding the
> features included in this patch.  I sent it in long ago

The folks at Qualcomm seem comatose about picking up most recent
patches, which is one of the reasons I'm offended about Qpopper LX being
announced.

They'd be useful even if in a contrib directory. It saves reinventing
the wheel in 40-50 different locations.

AB




RE: too many popper processes

2001-01-15 Thread Vigilante, Anthony

 Jeff,

Did you develop this patch?

-Original Message-
From: Jeff Earickson
To: Vigilante, Anthony
Cc: Subscribers of Qpopper
Sent: 1/15/01 10:54 AM
Subject: Re: too many popper processes

Hi,

The attached file is my patchfile to 3.1.2.  Among the several
additional
features is the "with-loadlimit" feature, which is what you want/need.

The folks at Qualcomm seem comatose about picking up and adding the
features included in this patch.  I sent it in long ago

** Jeff A. Earickson, Ph.D PHONE: 207-872-3659
** Senior UNIX Sysadmin, Information TechnologyEMAIL:
[EMAIL PROTECTED]
** Colby College, 4214 Mayflower Hill,   FAX: 207-872-3555
** Waterville ME, 04901-8842



 <<>> 



RE: too many popper processes

2001-01-15 Thread Jeff Earickson

yes.

** Jeff A. Earickson, Ph.D PHONE: 207-872-3659
** Senior UNIX Sysadmin, Information TechnologyEMAIL: [EMAIL PROTECTED]
** Colby College, 4214 Mayflower Hill,   FAX: 207-872-3555
** Waterville ME, 04901-8842


On Mon, 15 Jan 2001, Vigilante, Anthony wrote:

> Date: Mon, 15 Jan 2001 11:15:39 -0500
> From: "Vigilante, Anthony" <[EMAIL PROTECTED]>
> To: 'Jeff Earickson ' <[EMAIL PROTECTED]>
> Cc: 'Subscribers of Qpopper ' <[EMAIL PROTECTED]>
> Subject: RE: too many popper processes
>
>  Jeff,
>
> Did you develop this patch?
>
> -Original Message-
> From: Jeff Earickson
> To: Vigilante, Anthony
> Cc: Subscribers of Qpopper
> Sent: 1/15/01 10:54 AM
> Subject: Re: too many popper processes
>
> Hi,
>
> The attached file is my patchfile to 3.1.2.  Among the several
> additional
> features is the "with-loadlimit" feature, which is what you want/need.
>
> The folks at Qualcomm seem comatose about picking up and adding the
> features included in this patch.  I sent it in long ago
>
> ** Jeff A. Earickson, Ph.D PHONE: 207-872-3659
> ** Senior UNIX Sysadmin, Information TechnologyEMAIL:
> [EMAIL PROTECTED]
> ** Colby College, 4214 Mayflower Hill,   FAX: 207-872-3555
> ** Waterville ME, 04901-8842
> 
> 
>
>  <<>>
>




Re: too many popper processes

2001-01-15 Thread Jeff Earickson

Hi,

The attached file is my patchfile to 3.1.2.  Among the several additional
features is the "with-loadlimit" feature, which is what you want/need.

The folks at Qualcomm seem comatose about picking up and adding the
features included in this patch.  I sent it in long ago

** Jeff A. Earickson, Ph.D PHONE: 207-872-3659
** Senior UNIX Sysadmin, Information TechnologyEMAIL: [EMAIL PROTECTED]
** Colby College, 4214 Mayflower Hill,   FAX: 207-872-3555
** Waterville ME, 04901-8842




# This is a patch for qpopper3.1.2 to update it to qpopper3.2.2
# 
# To apply this patch:
# STEP 1: Chdir to the source directory.
# STEP 2: Run the 'applypatch' program with this patch file as input.
#
# If you do not have 'applypatch', it is part of the 'makepatch' package
# that you can fetch from the Comprehensive Perl Archive Network:
# http://www.perl.com/CPAN/authors/Johan_Vromans/makepatch-x.y.tar.gz
# In the above URL, 'x' should be 2 or higher.
#
# To apply this patch without the use of 'applypatch':
# STEP 1: Chdir to the source directory.
# If you have a decent Bourne-type shell:
# STEP 2: Run the shell with this file as input.
# If you don't have such a shell, you may need to manually create
# the files as shown below.
# STEP 3: Run the 'patch' program with this file as input.
#
# These are the commands needed to create/delete files/directories:
#
touch 'popper/dce_pwent.c'
chmod 0600 'popper/dce_pwent.c'
touch 'popper/pop_authdce.c'
chmod 0600 'popper/pop_authdce.c'
#
# This command terminates the shell and need not be executed manually.
exit
#
 End of Preamble 

 Patch data follows 
diff -c 'qpopper3.1.2/INSTALL' 'qpopper3.2.2/INSTALL'
Index: ./INSTALL
*** ./INSTALL   Tue Oct 10 19:10:23 2000
--- ./INSTALL   Tue Nov 21 10:17:56 2000
***
*** 191,197 
  
   --with-warnings  Enable additional compiler warnings.
  
!  --enable-hash-spool=1|2  Use hashed spool directory.  See 
HASH_SPOOL in section MACROS for more
information.  The default method is 2.
   
--- 191,198 
  
   --with-warnings  Enable additional compiler warnings.
  
!  --enable-hash-spool=1|2|3  
!   Use hashed spool directory.  See 
HASH_SPOOL in section MACROS for more
information.  The default method is 2.
   
***
*** 296,301 
--- 297,316 
   --disable-update-abort   Does not go into UPDATE state on abort.  Use
this to comply with RFC 1939.
  
+  --with-nonauth=path  Set the nonauthorized users file path.
+   Default is /etc/pop.nonauth.
+ 
+  --with-auth=path Set the authorized users file path.
+   Default is  /etc/pop.authorized.
+ 
+  --with-loadlimit=loadEnable loadlimit feature.  Load is the
+   numerical 1 minute load average, generally
+   seen via the user command "uptime".  
+   See LOADLIMIT in section MACROS for
+   more information.  Default = 16.0
+   Controllable at runtime option "-l" (see below).
+ 
+ 
  
  
  3. RUN-TIME OPTIONS (COMMAND LINE OPTIONS):
***
*** 306,314 
  
  The following are the command line options you can use.
  
! popper [-b bulldir [-B] [-c] [-d] [-D drac-host] 
 [-e login_delay=nn,expire=nn] [-f config-file] [-k] [-K service]
![-s] [-S] [-t trace-file] [-T timeout] [-u] [-R]
  
  Note that some systems may have limitations on the length or
  number of command line arguments in inetd.conf.  (For example,
--- 321,329 
  
  The following are the command line options you can use.
  
! popper [-a accesstime] [-b bulldir] [-B] [-c] [-d] [-D drac-host] 
 [-e login_delay=nn,expire=nn] [-f config-file] [-k] [-K service]
![-l load_ave] [-s] [-S] [-t trace-file] [-T timeout] [-u] [-R]
  
  Note that some systems may have limitations on the length or
  number of command line arguments in inetd.conf.  (For example,
***
*** 319,324 
--- 334,347 
  details, and the following section "RUN-TIME OPTIONS (CONFIG FILE)"
  for details.
  
+ -a accesstime  The minimum allowable access time between successive
+mail checks, specified in integer seconds.  This
+mechanism only works if KEEP_TEMP_DROP is defined,
+because the method compares the timestamp on the
+dropfile to the current time.  Used to keep people
+from beating on your POP server.  A small value
+(10 to 70 seconds) should be used.
+ 
  -b bulldir This is the locati