File: control

package info (click to toggle)
corekeeper 1.7
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye, buster, forky, sid, trixie
  • size: 84 kB
  • sloc: sh: 137; makefile: 9
file content (38 lines) | stat: -rw-r--r-- 1,430 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
Source: corekeeper
Section: admin
Priority: extra
Maintainer: Paul Wise <pabs@debian.org>
Build-Depends:
 debhelper (>= 9)
Standards-Version: 3.9.6
Vcs-Git: https://salsa.debian.org/debian/corekeeper.git
Vcs-Browser: https://salsa.debian.org/debian/corekeeper

Package: corekeeper
Architecture: kfreebsd-any linux-any
Pre-Depends:
 ${misc:Pre-Depends}
Depends:
 lsb-base (>= 3.2-14) [kfreebsd-any],
 procps [linux-any],
 ${misc:Depends}
Conflicts: core-dump-handler
Replaces: core-dump-handler
Provides: core-dump-handler
Description: enable core files and report crashes to the sysadmin
 corekeeper enables core files, reports crashes to the sysadmin and
 deletes old core files after 7 days.
 .
 Core file dumping is enabled for all users, to restrict that, please
 remove or edit the config file at /etc/security/limits.d/corekeeper.conf
 .
 On Linux core files are written to private per-userid dirs in /var/crash.
 Linux 3.6 and earlier have an issue that means all core files are written
 to the directory for root. If your system is running Linux 3.6 or earlier
 and is single-user (or you don't care about the privacy of core file names),
 you can avoid this issue by editing /etc/sysctl.d/corekeeper.conf.
 .
 On kFreeBSD files are written to /var/crash, kernel limitations prevent
 core files from being written to private per-userid dirs.
 .
 To fully remove this package it needs to be purged and the system rebooted.