Opened 8 years ago

Closed 8 years ago

#320 closed defect (fixed)

a version of kcore gets backed up

Reported by: JeffS Owned by: 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 (1)

mondoarchive.log.kcore.gz​ (71.0 KB) - added by JeffS 8 years ago.

Download all attachments as: .zip

Change History (6)

Changed 8 years ago by JeffS

comment:1 Changed 8 years ago by JeffS

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

comment:2 in reply to: ↑ description Changed 8 years ago 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

comment:3 Changed 8 years ago 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.

comment:4 Changed 8 years ago by bruno

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

comment:5 Changed 8 years ago by bruno

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.