*BSD News Article 52091


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!swidir.switch.ch!scsing.switch.ch!news.belwue.de!news.bawue.de!luva.lb.bawue.de!luva.lb.bawue.de!not-for-mail
From: migieger@luva.lb.bawue.de (Michael Giegerich)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: BSD/OS 2.0: spontaneous reboot triggered by user (program?)
Date: 26 Sep 1995 20:06:48 +0100
Organization: private BSD/OS site
Lines: 39
Message-ID: <449j08$fhg@luva.lb.bawue.de>
NNTP-Posting-Host: luva.lb.bawue.de


We provide internet access thru a BSD/OS 2.0.1 system mainly via
modem but also using ISDN dialins (thru a router).

I'm very pleased with the stability of BSD/OS: uptimes as long as
I want (if I hadn't to change/replace hardware from time to time).

One thing though puzzles me: I have two Amiga users (connected thru
modems) who are (better were) using a program called mlink (it pro-
vides screen functionality).
This program (compiled by them) after some time of operation nearly
for certain makes my system reboot. No messages, nothing than an im-
mediate reboot.
We (me and them) agreed on using screen in the future but yesterday
one of them arranged to make rebooting my system twice in less then
two hours :-(

I have read part of a thread about nearly the same problem (?) bet-
ween Win95 and BSD/OS some time ago - it seems I have missed the ans-
wer (if there was one).

Does anybody have information about this (Amiga's mlink and BSD/OS)?
Is there a solution? (The mlink source code is available - but I'm
not skilled enough to detect something out of it).

Could it be possible that disconnecting a modem unplugging it (in-
stead of using the normal procedure and logging out from the system)
will cause this result? (One of the users told me he had this impres-
sion. As this system is always very busy I can't afford to try this).

Is BSDI aware of these problems? (cc to them is set).

As one poster (don't remember its name) I too mean that no user program
should be able to crash a system.

BTW: FreeBSD-2.0R has the same problem (tested this with an other machine).

-- 
Michael Giegerich, E-Mail: migieger@luva.lb.bawue.de, Voice: +49 7144 39337