I'm trying to add "genric" #signal handling to #poser. Ultimate goal is to provide a way for #swad to handle #SIGHUP, although signal handling must be done in poser's main event loop (signals are only ever unblocked while waiting for file descriptor events).

Okay, I could just add explicit handling for SIGHUP. But a generic solution would be nicer. Just for example, a consumer might be interested in #SIGINFO which doesn't even exist on all platforms ... 🤔

Now, #POSIX specs basically just say signal constants are "integer values". Not too helpful here. Is it safe to assume an upper bound for signal numbers on "real world" OS implementations, e.g. 64 like on #Linux? Should I check #NSIG and, if not defined, just define it to 64? 🙈

#C #coding #question

today marks the 1 year anniversary of sigin.fo and I'm very happy about that :)

#SIGINFO

@parvXm

So you want no load line, but just the kernel stack? That'd require a kernel patch to change behavior. The idea of SIGINFO w/o the load line didn't make sense until the kernel stack stuff was added.

Why is the load line problematic?

#freebsd #stty #siginfo

Officially the owner of sigin.fo ! take that, Linux!

P.S. I'll probably be running a social media instance there.

#Unix #FreeBSD #SIGINFO

Today: I really, really, really wish #Linux had #SIGINFO.

#WinWithBSD