Opened 15 years ago
Closed 15 years ago
#320 closed defect (fixed)
a version of kcore gets backed up
Reported by: | JeffS | Owned by: | Bruno Cornec |
---|---|---|---|
Priority: | normal | Milestone: | 2.2.9 |
Component: | mondo | Version: | 2.2.8 |
Severity: | normal | Keywords: | |
Cc: |
Description
I have ntp running and discovered it creates the file /var/lib/ntp/proc/kcore. This file is a large file and becomes a biggiefile in mondo and so it gets backed up. If I turn off ntp during the backup that file is not there.
I think normally /proc/kcore is automagically skipped.
Attachments (1)
Change History (6)
by , 15 years ago
Attachment: | mondoarchive.log.kcore.gz added |
---|
comment:1 by , 15 years ago
Summary: | a version of kcore kets backed up → a version of kcore gets backed up |
---|
comment:2 by , 15 years ago
Status: | new → assigned |
---|
comment:3 by , 15 years ago
Just a note - see: http://forums.novell.com/novell-product-support-forums/suse-linux-enterprise-server-sles/sles-configure-administer/342245-giant-kcore-file.html
the ntp/proc is because ntp is chroot and needs it's own proc system. kcore is a memory image/access. All of ntp/proc should be skipped, I believe.
Just searching for the same question.
comment:5 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Replying to JeffS:
You can avoid that by adding a -E "/var/lib/ntp/proc" to your call of mondoarchive.
Too dep /proc mounted FS are not yet backed up. I need to see why the limit of the find command is maxdepth 3