For most of the morning I've been logged on to the server with my shell account and working on scripts with vi, but for the last hour or so, something keeps killing my vi process. It is very unnerving to get killed in the middle of changing a perl script. What is going on here? Who is killing my processes?

It just happened again!

And again. This is impossible, I can't work like this, every time I start vi, it gets killed in about 2 minutes. Are there script kiddies on the servers or something?

The same thing's happened to me off and on for the last few days on server19. It just happened within the last hour as well.

It's still happening, I was just using links and it got killed. I'm on server 21. Hostony staff, would you please respond? This is crazy.

In accord to our AUP you can't use more then 8% of processor time per minute.
If your proicess is killed it means that it was using more then 8%.

How could vi possibly use more than 8% of processor time?!?!?!?

Apparently it's the Moveable Type comment script that's a hog. This is very strange. How could a 774 byte perl script possibly be using so many resources?

#!/usr/bin/perl -w

# Copyright 2001-2003 Six Apart. This code cannot be redistributed without
# permission from www.movabletype.org.
#
# $Id: mt-comments.cgi,v 1.34 2003/02/12 01:05:31 btrott Exp $
use strict;

my($MT_DIR);
BEGIN {
if ($0 =~ m!(.*[/\\])!) {
$MT_DIR = $1;
} else {
$MT_DIR = './';
}
unshift @INC, $MT_DIR . 'lib';
unshift @INC, $MT_DIR . 'extlib';
}

eval {
require MT::App::Comments;
my $app = MT::App::Comments->new( Config => $MT_DIR . 'mt.cfg',
Directory => $MT_DIR )
or die MT::App::Comments->errstr;
local $SIG{__WARN__} = sub { $app->trace($_[0]) };
$app->run;
};
if ($@) {
print "Content-Type: text/html\n\n";
print "An error occurred: $@";
}