Skip to content
  • Categories
  • Recent
  • Tags
  • All Topics
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Uncategorized
  3. Bad default setting example: on #FreeBSD, core files are written in the working directory.
Welcome to Caint!

Issues? Post in Comments & Feedback
You can now view, reply, and favourite posts from the Fediverse. You can click here or click on the on the navigation bar on the left.

Bad default setting example: on #FreeBSD, core files are written in the working directory.

Scheduled Pinned Locked Moved Uncategorized
freebsd
2 Posts 2 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Nicolas MartyanoffG This user is from outside of this forum
    Nicolas MartyanoffG This user is from outside of this forum
    Nicolas Martyanoff
    wrote last edited by
    #1

    Bad default setting example: on #FreeBSD, core files are written in the working directory. Many daemons use "/nonexistent", so they cannot generate core files. So if they segfault, you won't have any idea why.

    Add kern.corefile=/var/coredumps/%U/%N.core to /etc/sysctl.conf.

    JeffO 1 Reply Last reply
    1
    0
    • Nicolas MartyanoffG Nicolas Martyanoff

      Bad default setting example: on #FreeBSD, core files are written in the working directory. Many daemons use "/nonexistent", so they cannot generate core files. So if they segfault, you won't have any idea why.

      Add kern.corefile=/var/coredumps/%U/%N.core to /etc/sysctl.conf.

      JeffO This user is from outside of this forum
      JeffO This user is from outside of this forum
      Jeff
      wrote last edited by
      #2

      @galdor this should be done with care. It will cause the kernel to write potentially sensitive information to disk. So: hopefully those dumps go in a spot that only root can access. You consider only turning this on for reproducible problems. If you decide.to turn it on generally, consider tripping an alert if the crash dump directory isn't empty.

      1 Reply Last reply
      1
      0
      • R ActivityRelay shared this topic
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • All Topics
      • Popular
      • World
      • Users
      • Groups