Bug 73047 - up2date does not close fds
up2date does not close fds
Product: Red Hat Public Beta
Classification: Retired
Component: up2date (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Jay Turner
Depends On:
Blocks: 67217
  Show dependency treegraph
Reported: 2002-08-30 00:48 EDT by Scott Lamb
Modified: 2015-01-07 19:00 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-30 22:33:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
up2date's 384 open fds (38.59 KB, text/plain)
2002-08-30 01:46 EDT, Scott Lamb
no flags Details

  None (edit)
Description Scott Lamb 2002-08-30 00:48:48 EDT
Description of Problem:

up2date does not close fds for packages it is downloading. Default ulimit is
1024, so I think up2date will consistently fail to run if a system has that many
packages out of date. Particularly since this happens both with newly downloaded
files and ones already in /var/spool/up2date.

Version-Release number of selected component (if applicable):


How Reproducible:


Steps to Reproduce:
1. Run up2date with many updates to do.
2. Midway through the process, do a "lsof -p <PID> | less"

Actual Results:

There are lots and lots of open /var/spool/up2date/* files.

Expected Results:

Just the one it is working on is open.
Comment 1 Scott Lamb 2002-08-30 01:46:24 EDT
Created attachment 73884 [details]
up2date's 384 open fds
Comment 2 Adrian Likins 2002-08-30 22:33:42 EDT
hmm, indeed. should be fixed in 2.9.62
Comment 3 Scott Lamb 2002-09-07 14:15:05 EDT
Yep, works for me. (I checked 2.9.68.) Thanks.

Note You need to log in before you can comment on or make changes to this bug.