Hi Paul,
With kill -14 91418, I don't see any output add to tr.
% ps -elf | grep strace
0 S kellythw 480 1 0 80 0 - 58957 - Nov05 ? 00:00:00
strace -o tr ./a.out
0 S kellythw 3760 1 0 80 0 - 58957 - Nov05 ? 00:00:00
strace -o tr ./a.out
0 S kellythw 15709 1 0 80 0 - 58957 - Nov05 ? 00:00:00
strace -o tr ./a.out
0 S kellythw 93336 91418 0 80 0 - 58957 - 08:14 pts/9 00:00:00
strace -o tr ./a.out
% tail tr
chdir("confdir3") = 0
mkdir("confdir3", 0700) = 0
chdir("confdir3") = 0
mkdir("confdir3", 0700) = 0
chdir("confdir3") = 0
mkdir("confdir3", 0700) = 0
chdir("confdir3") = 0
mkdir("confdir3", 0700) = 0
chdir("confdir3") = 0
mkdir("confdir3", 0700
Is server issue? should I change to other rhel8 server and try the same?
Thanks,
Kelly
If you need support for DevX Tools: http://devxsupport.cisco.com/
Specifically, for NXOS, see -
https://wiki.cisco.com/display/NEXUSPMO/ContactingNexusOpsAndTools
On 11/5/20, 2:52 PM, "Paul Eggert" <egg...@cs.ucla.edu> wrote:
On 11/5/20 2:28 PM, Kelly Wang (kellythw) wrote:
> When strace hang, I do 'ps -elf | grep strace' from other terminal and do
kill -9 <process id from ps -elf>
> kill -s INT $(ps -o pid= -C a.out) looks like not working from my server.
Assuming you're using the Linux kernel signal numbers, you should be able
to get
a process ID (say, 4729) and use this:
kill -2 4729
instead of the fancier 'kill' command I suggested. Also, try this in
another
session:
kill -14 4729
which sends the ALRM signal instead of the INT signal. Either way, see what
'tr'
says.
