pakfire: Don't mess with rlimit

This should not be here, because we will run this in the Python module
which is loaded by some other process. If anything we should only set
this on processes that we control, but currently I have never run into
this becoming a problem.

Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

diff --git a/src/pakfire/pakfire.c b/src/pakfire/pakfire.c
index 4faecaf431e9a32e869785809978b2454cb83471..6a7d90f200ee496daefb134e06f6b989a1273bde 100644 (file)
--- a/src/pakfire/pakfire.c
+++ b/src/pakfire/pakfire.c
@@ -996,11 +996,6 @@ int pakfire_create(struct pakfire** pakfire, struct pakfire_ctx* ctx,
        if (*p->distro.slogan)
                DEBUG(p->ctx, "    slogan     = %s\n", p->distro.slogan);
 
-       // Bump RLIMIT_NOFILE to maximum
-       r = pakfire_rlimit_set(p->ctx, PAKFIRE_RLIMIT_NOFILE_MAX);
-       if (r)
-               goto ERROR;
-
        // Return the pointer
        *pakfire = pakfire_ref(p);