I tried to kill it with various signals and it ignores -1, -15, -9, etc. Even if it ignored signals (which nothing in the process should do), it should have finished within ~12 hours, so it's borked.
I sent a message to OSUOSL support on Dec 30 about it but got no reply other than a ticket number (28099). Dana On Sat, Jan 2, 2016 at 2:40 AM, Markus Trippelsdorf <mar...@trippelsdorf.de> wrote: > There is a runway process on gcc112 that uses almost all of its > available memory: > > 133792 danaj 20 0 206G 201G 1728 R 99.9 79.1 101h perl > -Iblib/lib -Iblib/arch /home/danaj/trp2.pl 1049 > > The OOM killer tried to kill it, but unfortunately the process > apparently doesn't respond to SIGTERM. > > Could an admin (or danaj) please send a SIGKILL to the process? > > Thanks. > > -- > Markus > > _______________________________________________ > Gcc-cfarm-users mailing list > Gcc-cfarm-users@gna.org > https://mail.gna.org/listinfo/gcc-cfarm-users >
_______________________________________________ Gcc-cfarm-users mailing list Gcc-cfarm-users@gna.org https://mail.gna.org/listinfo/gcc-cfarm-users
