bleistift2@sopuli.xyz to Programmer HumorEnglish · 4 days agoThinking I could clean up my files in a SIGINT handlersopuli.xyzimagemessage-square46fedilinkarrow-up1397arrow-down14
arrow-up1393arrow-down1imageThinking I could clean up my files in a SIGINT handlersopuli.xyzbleistift2@sopuli.xyz to Programmer HumorEnglish · 4 days agomessage-square46fedilink
minus-squarebleistift2@sopuli.xyzOPlinkfedilinkarrow-up2·3 days agoI did try to catch all of these signals: | "SIGABRT" | "SIGALRM" | "SIGBUS" | "SIGCHLD" | "SIGCONT" | "SIGFPE" | "SIGHUP" | "SIGILL" | "SIGINT" | "SIGIO" | "SIGIOT" | "SIGKILL" | "SIGPIPE" | "SIGPOLL" | "SIGPROF" | "SIGPWR" | "SIGQUIT" | "SIGSEGV" | "SIGSTKFLT" | "SIGSTOP" | "SIGSYS" | "SIGTERM" | "SIGTRAP" | "SIGTSTP" | "SIGTTIN" | "SIGTTOU" | "SIGUNUSED" | "SIGURG" | "SIGUSR1" | "SIGUSR2" | "SIGVTALRM" | "SIGWINCH" | "SIGXCPU" | "SIGXFSZ" | "SIGBREAK" | "SIGLOST" | "SIGINFO";
minus-squarebleistift2@sopuli.xyzOPlinkfedilinkEnglisharrow-up1·2 days agoYep, in newer versions of node even attempting to do so will terminate the process.
I did try to catch all of these signals:
| "SIGABRT" | "SIGALRM" | "SIGBUS" | "SIGCHLD" | "SIGCONT" | "SIGFPE" | "SIGHUP" | "SIGILL" | "SIGINT" | "SIGIO" | "SIGIOT" | "SIGKILL" | "SIGPIPE" | "SIGPOLL" | "SIGPROF" | "SIGPWR" | "SIGQUIT" | "SIGSEGV" | "SIGSTKFLT" | "SIGSTOP" | "SIGSYS" | "SIGTERM" | "SIGTRAP" | "SIGTSTP" | "SIGTTIN" | "SIGTTOU" | "SIGUNUSED" | "SIGURG" | "SIGUSR1" | "SIGUSR2" | "SIGVTALRM" | "SIGWINCH" | "SIGXCPU" | "SIGXFSZ" | "SIGBREAK" | "SIGLOST" | "SIGINFO";
Good luck trapping the SIGKILL signal
Yep, in newer versions of node even attempting to do so will terminate the process.