OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
(fwd) Soft rlimit preferred to hard

From: LaMont Jones (lamonthp.com)
Date: Mon Apr 21 2003 - 12:39:57 CDT


Forwarded for a Debian developer not on the list. Please cc him on
replies.

lamont

-- forwarded message --
Subject: Soft rlimit preferred to hard
Date: Mon, 21 Apr 2003 17:26:18 +0000 (UTC)
Organization: Hewlett-Packard Company
Lines: 55
Sender: lamontcranston.fc.hp.com
Message-ID: <20030421172244.GA4127terpstra.ca>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB"
Cc: lamontdebian.org
To: postfix-userspostfix.org
X-Virus-Scanned: by amavisd-new-20030314-p1 (Debian)

--DocE+STaALJfprDB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Greetings!

I recently discovered that postfix implements mailbox quotas with an rlimit.
First off, let me say, I think this is a good idea since child processes
can't accidentally stray over the limit during procmail, etc.

However, I think this limit is enforced too stringently.

Of particular interest to me is being able to access a database during the
delivery rule of a procmail filter. If a delivery rule opens the database to
do some processing, it will die with SIGXFSZ even though the mailbox limit
is observed. This is because a RLIMIT_FSIZE applies to all files and uses.

I believe that filesystem-level quotas are what should enforce a 'hard' disk
quota. Thus, I would prefer:

- rlim.rlim_cur =3D rlim.rlim_max =3D limit;
+ rlim.rlim_cur =3D limit;

Then, applications which really know they should be avoiding postfix's
rlimit could still operate inside it.

I understand that root can change this limit, but as a user, there is little
one can do. This is the position I find myself in.

Please remove the hard limit, but leave the soft, and I think postfix will
be more widely useful under more arcane mail configurations.

Thank you.

PS. I am not subscribed to this list, so please CC me.

--=20
Wesley W. Terpstra <wesleyterpstra.ca>

--DocE+STaALJfprDB
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+pCjjvLvElXGKklYRAtBtAJ95xZY74CHLAowM6pdNhxI7ogim1gCfZQEL
c3tljANOv6fZqKZjCPHgbTU=
=ttST
-----END PGP SIGNATURE-----

--DocE+STaALJfprDB--
-- end of forwarded message --