Bug 52901 - klogd keeps System.map open
Summary: klogd keeps System.map open
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sysklogd
Version: 7.1
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-30 18:35 UTC by Pete Zaitcev
Modified: 2014-03-17 02:23 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2002-01-25 03:59:35 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:348 normal SHIPPED_LIVE Updated sysklogd package 2004-08-18 04:00:00 UTC

Description Pete Zaitcev 2001-08-30 18:35:12 UTC
Description of Problem:

On a system with /boot separated, it is not possible to unmount
it until klogd is killed.

Actual Results:

[root@mellorn zaitcev]# lsof -p 335
COMMAND PID USER   FD   TYPE     DEVICE    SIZE   NODE NAME
klogd   335 root  cwd    DIR        3,6    4096      2 /
klogd   335 root  rtd    DIR        3,6    4096      2 /
klogd   335 root  txt    REG        3,6   20380 502961 /sbin/klogd
klogd   335 root  mem    REG        3,6  434945 356930 /lib/ld-2.1.92.so
klogd   335 root  mem    REG        3,6 4776568 356937 /lib/libc-2.1.92.so
klogd   335 root    0r   REG        0,1       0      5 /proc/kmsg
klogd   335 root    1u  unix 0xcf4f4000            508 socket
klogd   335 root    2r   REG        3,1  213234     21
/boot/System.map-2.2.16-22smp
[root@mellorn zaitcev]# cat /etc/redhat-release 
Red Hat Linux release 7.0 (Guinness)


Additional Information:


Same story on Fairfax. Does anyone have an explantion why
to keep the System.map open? As far as I know, it is only
needed to print backtraces upon oops.

Comment 1 Bill Nottingham 2002-01-25 03:59:29 UTC
That is the only reason, and with kksymoops, it's somewhat irrelevant.

Comment 2 Bill Nottingham 2002-03-12 21:31:25 UTC
leak fixed in sysklogd-1.4.1rh-5.

Comment 3 John Flanagan 2004-08-18 14:55:30 UTC
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-348.html



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