Date: Fri, 5 Jun 2020 04:19:09 +0200 From: Kamil Rytarowski <ka...@netbsd.org> Message-ID: <99440f2e-c0fc-5e47-4f8b-137bdf5a3...@netbsd.org>
| I can see the problem now. It's a fault in ksh(1). Whether this actually amounts to being called a "fault" or not is not so clear ... most systems don't name the RT signals, that appears to be a BSD affectation. Even on NetBSD, when using bosh ()available in pkgsrc) the results are ... bosh $ kill -l HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM URG STOP TSTP CONT CHLD TTIN TTOU IO XCPU XFSZ VTALRM PROF WINCH INFO USR1 USR2 PWR RTMIN RTMIN+1 RTMIN+2 RTMIN+3 RTMIN+4 RTMIN+5 RTMIN+6 RTMIN+7 RTMIN+8 RTMIN+9 RTMIN+10 RTMIN+11 RTMIN+12 RTMIN+13 RTMIN+14 RTMIN+15 RTMAX-14 RTMAX-13 RTMAX-12 RTMAX-11 RTMAX-10 RTMAX-9 RTMAX-8 RTMAX-7 RTMAX-6RTMAX-5 RTMAX-4 RTMAX-3 RTMAX-2 RTMAX-1 RTMAX bosh $ (ignoring the funky formatting, made worse by my cut & paste). In POSIX, just SIGRTMIN and SIGRTMAX are defined (and "kill" is required to drop the SIG part) so bosh just invents "names" based upon those two. kre ps: in modern NetBSD, you might want to try /bin/sh as your interactive shell, it does most of what ksh can do (which is useful interactively, there's no "select" command, but I can't imagine that being of interactive use .. or actually of any real use). If there's some particular impediment, something lacking that you feel is required (something ksh can do which sh cannot) let me know, and if it seems reasonable, it could be added.