|
Grex > Helpers > #134: Grex System Problems - Summer 2004 |  |
|
| Author |
Message |
| 25 new of 286 responses total. |
albaugh
|
|
response 146 of 286:
| 
Aug 28 19:31 UTC 2004 |
The one limitation of backing up to disk is that it would still be in close
proximity to the master, so if a disaster struck the pumpkin there would be
no off-site storage to recover from.
|
gregb
|
|
response 147 of 286:
|
Aug 28 21:54 UTC 2004 |
Why is SunOS used as opposed to Linux or BSD?
|
jor
|
|
response 148 of 286:
|
Aug 28 23:51 UTC 2004 |
runs on a SUN
|
janc
|
|
response 149 of 286:
|
Aug 29 03:44 UTC 2004 |
Next Grex runs on OpenBSD.
Grex opened for business on July 18, 1991. Linus Torvald released the very
first version of Linux about two months later. ("Hello everybody out there
using minix - I'm doing a (free) operating system (just a hobby, won't be
big and professional like gnu) for 386(486) AT clones.") Somehow, the
founders didn't seem to think Linux was quite ready for the job at the time.
I'm not exacty sure what the situation was with BSD in 1991, but it wasn't
an option the founders were likely to have spent an awful lot of time
thinking about either.
|
keesan
|
|
response 150 of 286:
|
Aug 29 09:13 UTC 2004 |
So what OS did first grex use? And what hardware?
|
remmers
|
|
response 151 of 286:
|
Aug 29 14:14 UTC 2004 |
The hardware was a Sun 2, running SunOS (I forget which version).
Jan's right - Linux didn't exist yet, BSD wasn't easily available at low
cost, and we did have access to Sun (which was regarded as the Cadillac
of Unixes at the time).
Times have changed though, and I'm glad we're making the switch to x86
hardware and BSD.
|
janc
|
|
response 152 of 286:
|
Aug 29 14:56 UTC 2004 |
I think the first open source version of BSD, BSD/386 was also released in
1991. It too would have been horribly inadequate for Grex's needs. FreeBSD,
NetBSD, and OpenBSD were all years later.
I presume that it was SunOS 4.1.3 on the Sun 2. The differences between
that and the SunOS 4.1.4 running on this system are entirely unnoticable.
Mostly bug fixes.
At the time, SunOS was clearly the most stable, most capable version of
Unix available in our price range (probably in any price range). It's
still a remarkably solid piece of software. For me the main reason to
move off it is that too many of the open source packages that we want to
use (like mysql) no longer compile on SunOS.
|
dpc
|
|
response 153 of 286:
|
Aug 30 14:34 UTC 2004 |
Thanks to Kip, STeve and Jan!
|
tsty
|
|
response 154 of 286:
|
Aug 30 17:14 UTC 2004 |
nice job ... we all appreciate the efforts and results -thank you
|
mfp
|
|
response 155 of 286:
|
Aug 31 19:55 UTC 2004 |
Hi, all! I was in Ann Arbor! I ate at the Fleetwood!
|
happyboy
|
|
response 156 of 286:
|
Aug 31 20:13 UTC 2004 |
i'm sorry.
i use to work there. yuk.
|
tod
|
|
response 157 of 286:
|
Aug 31 20:18 UTC 2004 |
I used to consume hippy hash served by a tracked up Lisa. The coffee sucked
but they had a torlet so what the hell.
|
happyboy
|
|
response 158 of 286:
|
Aug 31 20:29 UTC 2004 |
i remember some of the grafitti from the torlet:
"The Fleetwood makes me shit PURE WATER SHIT."
accompanied by a childlike drawing of a screaming
person sitting on a torlet.
the cook use to pork his girlfriend in the storeroom and would
ash his ciggies in the chilipot.
bon appetit!
|
tod
|
|
response 159 of 286:
|
Aug 31 20:48 UTC 2004 |
We put a arbornet sticker in that torlet..wonder if its still there
|
naftee
|
|
response 160 of 286:
|
Sep 1 03:38 UTC 2004 |
INSIDE the torlet? Highly unlikely it survived.
|
gregb
|
|
response 161 of 286:
|
Sep 1 14:47 UTC 2004 |
Getting back to "Grex System Problems..."
In Backtalk, I disabled the "Favorites" items, but my listings are still
being seperated.
|
keesan
|
|
response 162 of 286:
|
Sep 2 23:16 UTC 2004 |
I am using procmail filter and I turned on the verbose part to figure out why
I get messages about locked filters:
Locking "var/spool/mail/k/e/keesan.lock"
Procmail: Error while writing to "/var/spool/mail/k/e/_w30Ggrex.cybe"
I get several of the above line then it unlocks things, every time. Why?
|
gelinas
|
|
response 163 of 286:
|
Sep 3 03:09 UTC 2004 |
The error occurs because you don't (and shouldn't) have 'write' access to the
directory /var/spool/mail/k/e/ . The file "/var/spool/mail/k/e/_w30Ggrex.cybe"
doesn't exist.
|
keesan
|
|
response 164 of 286:
|
Sep 3 13:48 UTC 2004 |
Have I set up .procmailrc wrong? Why it is trying to do something it should
not do? MAIL=/var/spool/mail/k/e/keesan is my first line of the filter, which
is no longer working to catch spams. Maybe I broke it? But I was frequently
getting these lock messages before and about 1-2 spams a day that should have
been caught were not, and now ALL of the spams are getting through (8 in the
last 5 hours or so). I would appreciate if you could take a look at the
filter, or I could post the complete (verbose) log file for one spam. I am
wondering if this is something to do with the grex revival (a bug).
|
keesan
|
|
response 165 of 286:
|
Sep 3 14:55 UTC 2004 |
I checked my log and every single message (none of which were caught by the
filter) says I had a lock failure. I think previously only the ones that the
spam filter missed said that. Has something changed at grex or did I mess
up my filter? .procmailrc
|
keesan
|
|
response 166 of 286:
|
Sep 3 20:04 UTC 2004 |
Here is a typical entry in my log file
procmail: Lock failure on "/var/spool/mail/k/e/keesan.lock"
From dmawllet@hotmail.com Fri Sep 3 10:54:30 2004
Subject: Cailis for $6 ($3 a dose)
Folder: /var/spool/mail/k/e/keesan 925
When I get the lock failure, the spam is not filtered to /dev/null as it
should be. What is causing the lock failure and how can I (or staff) fix
it?. This is 10 times as bad as it was before the grex disaster.
Todd, are you having spam filter problems (you use my filter, I think).
|
keesan
|
|
response 167 of 286:
|
Sep 3 20:17 UTC 2004 |
I think I caught the problem - I am sending anything Received from ... grex
or cyberspace to my inbox and this part of the header includes not only the
sender's but also the recipient's address. Sorry to bother people but I still
don't understand the 'lock' business.
|
gelinas
|
|
response 168 of 286:
|
Sep 4 02:39 UTC 2004 |
According to the man page for procmailrc, the format of a block is:
:0 [flags] [ : [locallockfile] ]
<zero or more conditions (one per line)>
<exactly one action line>
In some cases, you do not have a newline immediately following the
second colon. For example:
:0:
* ^Received:.*zillion
/dev/null
Has a couple of spaces at the end of the first line. I don't know that the
spaces are significant, since I haven't tried to correlate the messages that
cause lock errors with specific blocks in your .procmailrc. Neither have
I looked at every block to see if you have specified a lockfile somewhere.
|
keesan
|
|
response 169 of 286:
|
Sep 4 05:58 UTC 2004 |
Thanks, I will delete spaces on a line after the :. How did you find them?
Is there some way to view them with pico?
Can I put all the lines beginning with * ^ in between just a single
I have no idea how to specify a lockfile.
|
tpryan
|
|
response 170 of 286:
|
Sep 4 23:08 UTC 2004 |
I'm no expert, but my the man, as I read the notation, if a
locallockfile is used, the colon must precede it. That structure is
optional, so the trailing colon should probably be removed, as it may
be thinking your locallockfile is named ' '.
|