|
|
| Author |
Message |
| 20 new of 44 responses total. |
i
|
|
response 25 of 44:
| 
May 25 21:21 UTC 2001 |
Could you provide some details and specifics?
|
steve
|
|
response 26 of 44:
|
May 25 23:22 UTC 2001 |
There are no more errors from sd4 since the reboot. The strange
errors could be lots of things. Details will help us figure out
what they are...
|
steve
|
|
response 27 of 44:
|
May 26 00:13 UTC 2001 |
Grex had a vandal attack today which actually managed to do
something. It was reminiscent of the old "fork bomb" days of
old; I managed to kill it and the vandal, but we still have to
figure what this dear little character did.
In the mean time, I'd forgotten about the /etc/nlogin file
I'd put into place to keep further logins off Grex, so we were
disallowing logins for about 50 minutes where we should have
been allowing them. Sorry about that...
Thanks to dea for informing me both of the initial attack and
my successive forgetfulness.
|
russ
|
|
response 28 of 44:
|
May 26 18:31 UTC 2001 |
STeve et al...
When the "nologin" is in effect, the modems hang up before
they've had a chance to dump their data. Because of this,
in two calls all I saw of the message that's supposed to
be displayed was "Sorry"; the rest of it was lost in noise.
Can you please fix this feature so it delays a couple seconds
for the data to actually be delivered to the user? Better yet:
if you're not allowing logins, just drop DTR to the modems so
they don't answer.
|
lionfish
|
|
response 29 of 44:
|
May 26 18:52 UTC 2001 |
Re 27 - The fork bomb is remarkably easy to do - to test it i did it on my
linux machines upstairs. I dunno how to protect a machine from the forkbomb
(apart from disconneting the telnet port) - i'm thinking of setting up a
telnet server in the UK after the exams - but i want to learn how to protect
my computer from these attacks.
I'm wondering if the grex staff (who have a lot of experience with security
etc) might point me in the right direction on the net etc. Thanks for the help
From Lionfish.
|
scott
|
|
response 30 of 44:
|
May 26 20:47 UTC 2001 |
We're protected from most ways of doing a fork bomb, thanks to some special
code Marcus stuck into the fork() call. But once in a while somebody gets
creative and finds a way.
|
mdw
|
|
response 31 of 44:
|
May 27 00:03 UTC 2001 |
The recent vandal attack wasn't a "fork bomb". Grex has a kernel module
that hooks the "fork" call and looks for excessive fork failures. The
code is SunOS 4 specific as written; it could probably be ported to
OpenBSD and maybe Linux but won't be useful to anyone who isn't
interested in or already knows about how to write kernel load modules
for their OS.
|
janc
|
|
response 32 of 44:
|
May 28 06:52 UTC 2001 |
I was in the pumpkin today with Mark doing an inventory. While I was at it,
I snapped some pictures with my digital camera and generated a new, updated
Pumpkin tour page. The old one had four-year old pictures. The new one
is at http://www.wwnet.net/~janc/grextech/pumpkin/
|
n8nxf
|
|
response 33 of 44:
|
May 29 12:29 UTC 2001 |
Lovely!
|
aruba
|
|
response 34 of 44:
|
May 29 16:03 UTC 2001 |
A very nice page, Jan. Thanks for doing it.
|
janc
|
|
response 35 of 44:
|
May 29 17:19 UTC 2001 |
As a special added treat, the tour includes a picture of Mark taking
inventory.
|
tsty
|
|
response 36 of 44:
|
May 31 03:29 UTC 2001 |
great pages, really - thankxx
|
janc
|
|
response 37 of 44:
|
Jun 5 21:02 UTC 2001 |
I have successfully installed a second SCSI controller in Grex. I hooked up
to it a recently donated drive bay containing seven disk drives, each holding
a bit more than 4 Gig. The drives still need to be formatted, partitioned,
and tested before Grex can actually start using them, but I think we are
getting pretty close to being able to add a lot more disk to Grex than we'll
know what to do with for a while.
|
janc
|
|
response 38 of 44:
|
Jun 6 00:29 UTC 2001 |
% df
Filesystem kbytes used avail capacity Mounted on
/dev/sd6g 1969885 9 1772888 0% /mnt
/dev/sd6h 1971009 9 1773900 0% /mnt2
So now we just have to do some testing to convince us that this drive is
really OK, and then figure out what to do with it. One of the two partitions
might be a replacement for /c, which gave us a scare a while back (but has
shown no signs of problems since).
|
tpryan
|
|
response 39 of 44:
|
Jun 6 00:35 UTC 2001 |
If /c matches /a or /b, it might be worth thinking to re-assgn
/c, and use the drive as a hot spare for /a and /b.
Why do you call the Mount MNut?
|
gull
|
|
response 40 of 44:
|
Jun 6 02:49 UTC 2001 |
Tradition.
|
janc
|
|
response 41 of 44:
|
Jun 6 09:20 UTC 2001 |
/mnt is just a traditional name for a temporary mount point. I don't know
enough about the problem with /c to assess it, but if it is dubious, we should
just throw it away. We've got lots of disk. We son't need to fool with
anything dubious.
|
drew
|
|
response 42 of 44:
|
Jun 6 18:17 UTC 2001 |
How EVER did you manage to get a machine booted up and running with *only*
/mnt and /mnt2 mounted?
|
janc
|
|
response 43 of 44:
|
Jun 7 03:41 UTC 2001 |
Vi.
|
davel
|
|
response 44 of 44:
|
Jun 7 11:15 UTC 2001 |
Heh.
|
