home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!snorkelwacker.mit.edu!ai-lab!hal.gnu.ai.mit.edu!gwydion
- From: gwydion@hal.gnu.ai.mit.edu (Mercenary Programmer)
- Newsgroups: alt.irc
- Subject: Re: *die* monitor.ece.uiuc.edu
- Message-ID: <26573@life.ai.mit.edu>
- Date: 14 Aug 92 13:25:16 GMT
- References: <9220819.18246@mulga.cs.mu.OZ.AU>
- Sender: news@ai.mit.edu
- Organization: /etc/organization
- Lines: 24
-
- In article <9220819.18246@mulga.cs.mu.OZ.AU> thecure@ee.mu.OZ.AU (the cure) writes:
- >Can someone explain "exactly" why monitor.ece.uiuc.edu is on the net.
- >
- >Apparently it's just to take stats. This is easily done with an automated bot.
-
- It is? Would you care to write the aforementioned automated bot? A
- server will automatically receive all appropriate messages; all the
- monitor code has to do is to receive it. The same is not true for
- a bot.
-
- >I am only whinging, cause it hangs when you try and do any server stuff with it.
- >
- >(ie - /stats L monitor.ece.uiuc.edu does nothing.)
-
- It doesn't hang; the message is transmitted. Only monitor doesn't
- care, so it sends no messages back. Ever telnetted to a server,
- pretending to be a server yourself, and send /notify messages back
- to people who /trace you? Quite interesting, actually. One has
- to be a fast typist - or a good programmer. However, that is a
- side note - monitor is just a receptacle for messages, it has no
- reason to respond.
-
- Gwydion.
-
-