|
|
| Author |
Message |
| 25 new of 293 responses total. |
keesan
|
|
response 215 of 293:
| 
Feb 21 21:46 UTC 2002 |
Thanks, I will tell the chatter to wait 30 sec next time while I shell.
|
katie
|
|
response 216 of 293:
|
Feb 22 01:01 UTC 2002 |
For the record, I still think the person who invented 'talkdaemon'
should be lined up and shot.
|
jazz
|
|
response 217 of 293:
|
Feb 22 04:37 UTC 2002 |
Mesg's author, presumably, earned his pardon.
|
tsty
|
|
response 218 of 293:
|
Feb 22 15:28 UTC 2002 |
a !mesg N and then a quick restart of your chat <loginid>
will stop the problem. that also presumes yu haven't sent a tel to
your annoyer already.
|
keesan
|
|
response 219 of 293:
|
Feb 22 17:07 UTC 2002 |
Thanks, that sounds much easier than exiting chat and running the change
program. I did not know you could even shell from chat.
|
jp2
|
|
response 220 of 293:
|
Feb 22 17:59 UTC 2002 |
This response has been erased.
|
jhudson
|
|
response 221 of 293:
|
Feb 23 02:06 UTC 2002 |
Because only one kernel syscall can run at a time.
|
remmers
|
|
response 222 of 293:
|
Feb 23 15:44 UTC 2002 |
Not true. If *that* were so, lots of other things would be slow,
and a system call that didn't return would bring everything to a
stop.
|
mdw
|
|
response 223 of 293:
|
Feb 24 04:00 UTC 2002 |
Actually, only one kernel syscall can run at a time (at least under
sunos), but that's a moot point, since long-running system calls
typically block on some event and allow other things, including other
system calls, to use the CPU. None of this is particularly relevant to
why ps et al are slow -- the real reason is because sunos doesn't offer
the accellerators that later systems have to access kernel structures.
In SunOS, everything is done using "nlist" and "/dev/kmem"; on many more
recent systems, there is a kernel ksyms data structure and things in
/dev and /procfs that access the kernel ksyms data, and even more
usefully, stuff in the kernel that provides access to the process table,
per-user kernel data, and other stuff without the bother of going
through kmem. This is just one of the things that contributes to kernel
bloat in linux, solaris, etc.
|
keesan
|
|
response 224 of 293:
|
Feb 25 15:38 UTC 2002 |
Valerie kindly pointed out that there is no need to set up your own twit
filter, you can type 'ignore username'. I presume this holds for an
individual session. Is there some way to make it permanent for use when
someone has trashed all the items in a conference? I. e., can I put the line
in some file that runs whenever I use bbs?
|
rcurl
|
|
response 225 of 293:
|
Feb 25 15:46 UTC 2002 |
The spam rate here seems to be increasing. Is there a central spam filter
for incoming mail, for either source or recipient addresses (like
Undisclosed-Recipient@cyberspace.org)?
|
keesan
|
|
response 226 of 293:
|
Feb 25 16:01 UTC 2002 |
Ask Marcus, who is working on it. I forward my spams to him at UCE, with full
headers.
|
keesan
|
|
response 227 of 293:
|
Feb 25 16:07 UTC 2002 |
I am unable to connect with lynx to google, altavista, or alltheweb.
It says it is trying to connect to 123.45.567.78 (sample numbers) and nothing
happens for 60 sec. I Ctl-C to exit.
|
mdw
|
|
response 228 of 293:
|
Feb 25 21:45 UTC 2002 |
!finger uce
for more information on spam filters on grex. We purposefully don't
publish detailed information on the spam logic on grex, because we
don't want to educate spammers on how to evade them.
|
krj
|
|
response 229 of 293:
|
Feb 25 22:08 UTC 2002 |
resp:127 :: another lynx trouble report, from party:
stephenl: Does anyone know what is wrong with lynx?
stephenl: It won't connect to any websites. It always goes back to the
localhost.
I wiggled lynx a bit -- I usually don't run it -- and it does seem
to fail to connect to anything.
|
mdw
|
|
response 230 of 293:
|
Feb 25 23:32 UTC 2002 |
Apparently gryps bit the dust. Someone is supposed to go reboot it
tonight.
|
tnblaze
|
|
response 231 of 293:
|
Feb 27 10:38 UTC 2002 |
this is a tast since im new at this and i dont know how to work it yet lol
|
davel
|
|
response 232 of 293:
|
Feb 27 13:36 UTC 2002 |
Try joining the test conference ("j test"), if that's what you need to do.
|
tsty
|
|
response 233 of 293:
|
Feb 27 17:22 UTC 2002 |
re 224 .. ignore username works in party .. does it also
work in the real world? this would be interesting.
|
davel
|
|
response 234 of 293:
|
Feb 28 02:22 UTC 2002 |
Heh. TS, is picospan really realer than party? In the real world, ignoring
people sometimes works, sometimes not ...
<goes off & tries it>
As it stands, it does *not* hold for your current session, only for future
sessions; but it tells you how to make it take effect for the current session.
Someone wrote something to add twit-filter lines to your .cfonce (your bbs
startup script). Running it again for someone else will append another set
of lines, I think - so the net effect will be to replace any previous twit
filter. (You can, however, list all the users you want to ignore on one
command.)
Valerie or whoever wrote it, nice job.
<goes off & looks> Yep, Valerie.
|
tsty
|
|
response 235 of 293:
|
Mar 1 18:03 UTC 2002 |
for teh more adventurous (and before applying taliban tactics) there
is this missive i have unabashedly plagiarized from 'a player to
be named later .. if at all.'
"Unfortunately, the answer to "kick him off" is yes, but it wouldn't
help. All he would need to do then is run newuser & create himself
another account. So, in order to fight that, we'd have to have
somebody always watching, and pulling the plug as necessary.
It's a big brother cat-and-mouse game. No joy in that.
Actually, this is a behavior/socialiazation problem. There are
other methods of dealing with such problems that are far more
effective. The trick is to pull "orthogonal" thinking on him.
You can't just react to him (that plays right into his mindset)
and while sometimes it's possible to ignore him, that's not
always effective. Things that might work include applying logic
to what he says (most crude sayings are truely hilarious when
looked at the right way), or applying inventive logic to him.
There are some tricky knife edges to watch: he should never know
for sure if you are making fun of him or are being deadly
serious, and whatever you say should be at least mildly
entertaining to others. If you do it right, however,
you might find either (a) he undergoes a personality phase
shift and becomes an interesting person, or (b) he gets bored
and goes elsewhere to get his jolly's.
Please do send mail to staff if this doesn't suffice or if things get worse."
i believe the plagiarizm is character-for-character .. at least i hope so.
|
krj
|
|
response 236 of 293:
|
Mar 1 23:19 UTC 2002 |
Looks like user tikcloak is launching a new connection to Grex every
five minutes. If unchecked, this will be a problem in a couple of hours.
The regularity of the logins say to me this is an automatic process.
grex.cyberspace.org% finger tikcloak
Login: tikcloak Name: TikCloak
Directory: /a/t/i/tikcloak Shell: /usr/local/bin/bash
On since Fri Mar 1 17:30 (EST) on ttyp3 from 203.162.56.202
On since Fri Mar 1 17:45 (EST) on ttyp5 from 203.162.56.202
On since Fri Mar 1 16:55 (EST) on ttyp7 from 203.162.56.202
On since Fri Mar 1 17:00 (EST) on ttyp8 from 203.162.56.202
On since Fri Mar 1 17:05 (EST) on ttypb from 203.162.56.202
On since Fri Mar 1 17:20 (EST) on ttypd from 203.162.56.202
On since Fri Mar 1 17:50 (EST) on ttype from 203.162.56.202
On since Fri Mar 1 18:05 (EST) on ttypf from 203.162.56.202
On since Fri Mar 1 18:00 (EST) on ttyq2 from 203.162.56.202
On since Fri Mar 1 17:25 (EST) on ttyq3 from 203.162.56.202
On since Fri Mar 1 18:10 (EST) on ttyq7 from 203.162.56.202
On since Fri Mar 1 17:40 (EST) on ttyq9 from 203.162.56.202
On since Fri Mar 1 16:50 (EST) on ttyp0 from 203.162.56.202
On since Fri Mar 1 17:10 (EST) on ttyq0 from 203.162.56.202
On since Fri Mar 1 17:55 (EST) on ttyq4 from 203.162.56.202
On since Fri Mar 1 17:35 (EST) on ttyp9 from 203.162.56.202
On since Fri Mar 1 17:15 (EST) on ttyq1 from 203.162.56.202
No unread mail
No Plan.
|
carson
|
|
response 237 of 293:
|
Mar 2 02:37 UTC 2002 |
Further investigation suggests the user began this task early this
morning, with only minor outages. However, I do not share Kenneth's
pessimism, as I recall Grex has an auto-kill program for multiple
logins. At most, it is amusing.
|
jhudson
|
|
response 238 of 293:
|
Mar 2 02:53 UTC 2002 |
This is quite amusing. There are more efficent ways of bringing grex
down if someone really wanted to. (No, I won't demonstrate).
|
gelinas
|
|
response 239 of 293:
|
Mar 2 03:02 UTC 2002 |
The auto-kill doesn't kick until grex hits 70 remote users.
|
