Ticket #320 (closed defect: fixed)

Opened 2 years ago

Last modified 1 year ago

a version of kcore gets backed up

Reported by: JeffS Assigned to: bruno
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

mondoarchive.log.kcore.gz (71.0 kB) - added by JeffS on 02/22/09 19:15:47.

Change History

02/22/09 19:15:47 changed by JeffS

  • attachment mondoarchive.log.kcore.gz added.

02/22/09 19:16:52 changed by JeffS

  • summary changed from a version of kcore kets backed up to a version of kcore gets backed up.

(in reply to: ↑ description ) 03/19/09 02:19:15 changed by bruno

  • status changed from new to assigned.

Replying to JeffS:

I have ntp running and discovered it creates the file /var/lib/ntp/proc/kcore.

You can avoid that by adding a -E "/var/lib/ntp/proc" to your call of mondoarchive.

I think normally /proc/kcore is automagically skipped.

Too dep /proc mounted FS are not yet backed up. I need to see why the limit of the find command is maxdepth 3

03/25/09 17:09:20 changed by afbach

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.

04/30/09 18:22:42 changed by bruno

Should be solved by rev [2184]. Will be in 2.2.9.

06/15/09 21:20:14 changed by bruno

  • status changed from assigned to closed.
  • resolution set to fixed.