|
|
| Author |
Message |
rational
|
|
Aidez.
| 
Feb 23 02:32 UTC 2004 |
Grex's staff and board ignores important member concerns in E-mail. I could
sympathise with ignoring baseless or silly complaints, but that's not what
I'm talking about: I'm talking about them ignoring important issues I've
brought up in E-mail because I'd prefer not to discuss them in coop. Most
of the times, I've been completely ignored.
Have you ever read Grex's /etc/aliases? It's quite a doozy, quite complicated
for a file like that. But what's the point, if mail sent to those aliases
is ignored?
|
| 35 responses total. |
salad
|
|
response 1 of 35:
|
Feb 23 03:21 UTC 2004 |
What's the point of GreX at all, unless you're considered "special"
|
albaugh
|
|
response 2 of 35:
|
Feb 23 23:11 UTC 2004 |
BS. e-mail sent to staff of a legitimate nature sent by people not proven
by themselves to be twits is treated seriously and is reponded to. Can you
grok the implication?
|
rational
|
|
response 3 of 35:
|
Feb 23 23:51 UTC 2004 |
I already explained I'm talking about reasonable complaints, and not just
staff. Did you read what I wrote?
|
jaklumen
|
|
response 4 of 35:
|
Feb 24 00:03 UTC 2004 |
*yawn*
|
salad
|
|
response 5 of 35:
|
Feb 24 00:24 UTC 2004 |
Staff is ignoring like crazy
|
davel
|
|
response 6 of 35:
|
Feb 24 01:21 UTC 2004 |
Well, you drove away the one staff person most likely, by a large margin, to
respond to any particular complaint.
Otherwise, what albaugh said.
|
salad
|
|
response 7 of 35:
|
Feb 24 02:25 UTC 2004 |
It was all my fault, I admit.
That's why I asked for item 68 to be deleted.
But look, it hasn't been deleted.
Look who's the culprit now.
The staff, as usual.
|
janc
|
|
response 8 of 35:
|
Feb 24 03:41 UTC 2004 |
Actually, I think the staff member most likely to answer any message is Steve
Weiss, who has not been driven away. However he usually processes mail only
once a week and occasionally misses a week.
I never read any staff email. I should check my grex-box. Oops 2013 new
messages. Is that all?
|
salad
|
|
response 9 of 35:
|
Feb 24 04:47 UTC 2004 |
The recent stuff is important
|
rational
|
|
response 10 of 35:
|
Feb 24 04:56 UTC 2004 |
Not just staff, folks: board.
|
janc
|
|
response 11 of 35:
|
Feb 24 14:12 UTC 2004 |
I don't usually mess with this stuff, but I took a very quick look at
it. It looks to me like the locking of naftee's account was perfectly
ordinary. Naftee had lots of pointless processes running that drove
Grex's system load very high, making the system nearly unusable. The
system was so slow, Joe had difficulty logging in. I believe he went to
the pumpkin and got on the console to kill the processes. Killing
naftee's processes fixed the problem.
If I had some time to kill, I'd go look at what he was running in detail
and try to figure out why robocop didn't kill it, but it doesn't
particularly surprise me that it didn't. Robocop is really not that
smart, and trys to err on the side of not killing stuff.
I have no way of knowing if naftee was doing this to cause problems or
had some sensible end in mind and just screwed up. Running "fortune"
zillions of times with the output directed to /dev/null doesn't have any
obvious sensible application, but it isn't exactly a normal vandal
attack either.
Only think I can say in his favor is that naftee does not have a record
of doing this kind of crap. It might be reasonable to restore his
account if he'll be more careful in the future.
|
gelinas
|
|
response 12 of 35:
|
Feb 24 16:40 UTC 2004 |
(Yes, I had to go to the Pumpkin and use the console to log on to figure out
what was happening.)
|
rational
|
|
response 13 of 35:
|
Feb 24 16:54 UTC 2004 |
You really didn't. Grex was usuable, if incredibly slow.
|
gelinas
|
|
response 14 of 35:
|
Feb 24 17:13 UTC 2004 |
From off-site, I only use ssh, which could not open a connection.
After logging in from the console, I used telnet from another machine on
the network and discovered that there was a queue, even with fewer than
forty people logged in (I don't remember the exact number now).
Yes, a visit to the pumpkin was required.
|
rational
|
|
response 15 of 35:
|
Feb 24 20:55 UTC 2004 |
nope. i was able to use grex remotely just fine.
|
albaugh
|
|
response 16 of 35:
|
Feb 24 21:20 UTC 2004 |
Bully for you.
|
salad
|
|
response 17 of 35:
|
Feb 24 23:06 UTC 2004 |
I did manage to log onto GreX, but when I did a ps at the bash promt, I
only recieved the output of two jobs. Therefore I assumed that whatever
jobs I had before had ceased running and the high load averages were not
of my doing. I was unable to run top and kill the processes myself
though.
|
rational
|
|
response 18 of 35:
|
Feb 24 23:08 UTC 2004 |
gelinas is just impatient, and you paid for the trouble his impatience caused.
|
salad
|
|
response 19 of 35:
|
Feb 24 23:28 UTC 2004 |
I paid for the cost of a bug! At least janc mentioned he could look into the
problem, as apposed to gelinas, who just likes to QUASH USERS
|
salad
|
|
response 20 of 35:
|
Feb 24 23:29 UTC 2004 |
I hope janc finds some time to kill and puts some sensibility into this
senslelessnes.
|
rational
|
|
response 21 of 35:
|
Feb 24 23:35 UTC 2004 |
I'd like to know one thing gelinas has done as staff besides killing accounts.
|
other
|
|
response 22 of 35:
|
Feb 24 23:37 UTC 2004 |
21: Tough monkeys, bunghole.
|
mary
|
|
response 23 of 35:
|
Feb 25 00:17 UTC 2004 |
Our staff is doing a wonderful job of remaining cool and calm
and reasonable despite the baiting. Kudos, guys.
|
janc
|
|
response 24 of 35:
|
Feb 25 00:35 UTC 2004 |
Actually Joe does lots of useful stuff, including killing users. Staff
kills lots and lots of users. I used to do dozens a week when I was
still active. I thank Joe for his efforts. If I'd seen an account
running crap like that, I'd have locked it too.
If it was a mistake on your part, then it is possible to rectify the
mistake.
|