Slashdot Mirror


Worker Fired For Running SETI On State-Owned PCs

Formica writes "A programmer working for the Ohio Department of Job and Family Services was fired for running SETI software on a state server. As quoted in this article, department head Tom Hayes says, 'I think that people can be comfortable that security has beamed this man out of our building.' More articles from Google."

7 of 622 comments (clear)

  1. Re:Would you want to work for this guy? by genixia · · Score: 4, Interesting

    Maybe Tom won't be the only one 'beamed' out of the building.

    It's going to be amusing if he turns around and sues the state for slander. After all, it's been very publicly broadcast to millions of people that he's short of intelligence.

  2. Re:Would you want to work for this guy? by networkBoy · · Score: 5, Interesting

    The one thing to be noted is that running SETI on a server is unwise.
    While I have never seen a problem personally I enforce my company policy that it be kept off servers. Desktops/proto machines fine, just not production environment servers. We actually use it to increase load on pre-production servers though :-)
    -nB

    --
    whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
  3. Been there done that. by LTSharpe · · Score: 4, Interesting

    I had it running on 5 servers at one time at a gov agency I worked for. Soon it got around that SETI was running on 'production' servers and I was told politely to quit running it for all of the common reasons,, misuse of public funds etc. Keep in mind the servers were only using a fraction of their capability doing what they were doing in the first place,, and what they were doing was pretty useless and just bureacratic pork programs on a small scale.

  4. Re:He should be fired. He should be arrested! by lottameez · · Score: 5, Interesting

    dude, there is far more fraud, waste, and abuse in government then this piddling little thing. In the scheme of things, it probably cost more in administration costs to fire the poor bastard and hire a new guy than any expense brought on by the SETI program.

    --
    Yeah? Well I think you're overrated too.
  5. Beh by cookiepus · · Score: 4, Interesting

    Well, mixed feelings...

    On one hand what this guy did is clearly wrong - even according to SETI rules - you're warned not to run this shit on computer on which you're not allowed to do so.

    SETI uses up a lot of CPU cycles and makes outgoing network connections on its own (well he could have set it up in different ways, I guess) so it's dumb to have it run on a government SERVER without getting explicit permission.

    On the other hand - this sort of shit shouldn't get someone fired* - maybe some embarasing talking to followed by an office-wide memo reminding everyone that "in light of recent transgressions, PLEASE BE ADVISED not to do this kind of shit"

    *The stories that I've seen do not indicate whether there's been any prior incidents. Perhaps in this workplace, the "don't install shit on the server" policy is so ingrained into the office culture that someone can't be unaware of the severity of the consequences, in which case the firing is in order.

    But actually I hink the comments by Tom Hayes are truthful (but unprofessional). Someone who values his SETI workunit count to such an extent as to fuck around at work, isn't brilliant.

  6. Re:As a taxpayer... by dougmc · · Score: 4, Interesting
    Wasting _unused_ clock cycle[s]
    To be fair, even with the priority cranked all the way down, such a program does make other programs run slightly slower (and increases overall latency of the system.) Also, by keeping the CPU busy, the OS cannot execute the HLT (basically a nap of a few nanoseconds) operations, which allow it to save some energy and reduce the heat generated. A system running Seti uses more power than the same system being idle.

    And then there's the small amount of bandwidth used ...

    Running programs like Seti and RC5 is *not* free. Cheap, maybe, but not completely free.

  7. WRONG by alizard · · Score: 4, Interesting
    That is an exactly proper use for the tort mechanism.The administrator chose to attack his employee in public for no reason that a reasonable person would take seriously in a way that any reasonable person would expect to compromise the victim's ability to find future employment in his field.

    The organization that hired the meathead running the IT organization should be forced to pay out a multimillion dollar damage judgement. Unfortunately, this will come out ot the pockets of the taxpayers, not stockholders, but shit happens.