Terminal gets SIGHUP in Global Zone after 'npm' command is run
An OpenIndiana user has problem with the
npm -version in Global Zone. When the command finished, something gets
SIGHUP and whole terminal gets terminated:
... /1: write(20, " 6 . 1 3 . 4\n", 7) = 7 /1: write(20, 0xFFDF9A00, 0) = 0 /2: Received signal #1, SIGHUP, in port_getn() [default] /2: siginfo: SIGHUP pid=4727 uid=2903 /4: Received signal #25, SIGCONT, in lwp_park() [default] /3: Received signal #1, SIGHUP, in lwp_park() [default] /1: Received signal #24, SIGTSTP [default] /2: port_getn(10, 0xEED88EC0, 1024, 1, 0x00000000) Err#4 EINTR /3: lwp_park(0x00000000, 0) Err#4 EINTR
The user runs with very recent gate
This looks similar to a recent bug manifesting in local zone but the user has this one patched and this actually happens in the Global Zone.
I myself can't reproduce this.
Updated by Predrag Zečević 12 months ago
since this happens to me, I have to add here that this problem occurs only when using
terminator terminal. On
mate-terminal I did not noticed this error.
:; ps -ef -Z | grep te[r]minator global predrag* 1863 1805 1 12:11:03 ? 18:41 /usr/bin/python2.7 /usr/bin/terminator