[60266] in Hotline Meeting
Re: Case 287828: This case has recently been updated
daemon@ATHENA.MIT.EDU (Thomas H. Grayson)
Wed Jul 10 11:54:27 2002
Message-Id: <200207101554.LAA19842@n42-286-1.mit.edu>
To: "andrew m. boardman" <amb@MIT.EDU>
cc: hotline@MIT.EDU, ops@MIT.EDU, alexp@MIT.EDU, zacheiss@MIT.EDU
In-Reply-To: Your message of "Tue, 09 Jul 2002 22:55:10 EDT."
<200207100255.WAA20832@pothole.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 10 Jul 2002 11:54:23 -0400
From: "Thomas H. Grayson" <thg@MIT.EDU>
I also found that this software was running on n42-286-1. On this machine, at
least, the directory /var/local/seti/setiathome-3.03.i686-pc-linux-gnu-gnulibc2
.1 contains a README.local and a user_info.sah that identify Alex Prengel as
the person who set this up. Presumably he set it up on the other machine too,
although I haven't checked this. Here, /etc/init.d contains two seti entries,
watchedseti and watchedsetir. What caught my eye on the other box was that
the seti process was running full tilt while I was logged in trying to do
other things. Apparently, this is not supposed to happen. From the
README.local on n42-286-1:
5/24/01
The copy of seti@home running out of this directory is set to turn off
automatically within 30 sec. or less of a user login at the console,
running only a deamon to monitor user logins that consumes negligible
CPU time while anyone is logged in.
If you need to turn it off for any reason, su to root (using the
default Athena root password), and run:
/var/local/seti/current/stopwatchedseti
If there are any problems contact Alex Prengel (alexp@mit.edu, x3-8613).
Tom
> From: "andrew m. boardman" <amb@MIT.EDU>
> Date: Tue, 9 Jul 2002 22:55:10 -0400
> Subject: Re: Case 287828: This case has recently been updated
>
>
> >The Linux Athena workstation n42-203-1.mit.edu in N42-203 is
> >running the SETI at Home daemon, and the /etc/init.d/watchedsetir
> >starts it up automatically at boot.
>
> If someone with access to the machine can look at that script and find
> the directory from which the process runs, there should be a file there
> called user_info.sah. It contains a textual username (which could be
> null) and a unique user ID number which can be mapped to an email address.
> If they're actually a semilegitimate user, they may have left a README or
> similar with more information about what they think they're doing.
