Login
You're viewing the functional.cafe public feed.
  • Nov 17, 2026, 1:23 PM

    @tnorinder Honestly I don't think it's that bad! daemons were never supposed to run in a foreground process group, so I can't blame Apache devs for choosing to use SIGWINCH. It is, shall we say, an unfortunate interaction. 😅

    💬 1🔄 0⭐ 1

Replies

  • Nov 17, 2026, 4:44 PM
    @ska @tnorinder Yeah, although can be quite nice for debugging, specially when it's on a pre-supervision system (imagine trying to insert gdbserver/strace into Debian's humongous initscripts or even it's own random perl config-reading wrappers).
    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Nov 17, 2026, 7:43 PM

    @ska @tnorinder Yeah, although with the addition of SIGRTs that should be pretty rarely needed (8 of them minimum on a POSIX system, usually more like 20~30, see {RTSIG_MAX} in <limits.h>)
    And I guess beyond that one could go for things like sockets.

    💬 0🔄 0⭐ 0
  • Nov 17, 2026, 7:51 PM

    @lanodan @tnorinder Excuse me, only a psychopath would use real-time signals to send commands to daemons. This would be completely arbitrary.

    Imagine, for instance, deciding that the reboot signal for your init process must be SIGRTMAX+3. This is so absurd that everyone would laugh you out of the room.

    ... right?
    💬 0🔄 0⭐ 0