Path: utzoo!attcan!uunet!mcsun!hp4nl!svin02!eba!wjw
From: wjw@eba.eb.ele.tue.nl (Willem Jan Withagen)
Newsgroups: comp.sys.apollo
Subject: Re: os level 2 processes
Keywords: DPCI, Level 2 Processes
Message-ID: <842@eba.eb.ele.tue.nl>
Date: 12 Oct 90 14:07:00 GMT
References: <9010111252.AA02899@gw1.ags.bnl.gov>
Sender: news@eb.ele.tue.nl (The News system)
Organization: Eindhoven University of Technology, The Netherlands
Lines: 24

In article <9010111252.AA02899@gw1.ags.bnl.gov> roger@GW1.AGS.BNL.GOV (Roger A. Katz) writes:
>I have no idead whether this is related to other peoples problems but we
>saw this on the node we were using for a dpci server. whenever our pc users
>would turn off their machines, with out first logging off from dpci, the
>server node would be left with these level 2 processes. re-booting was the
>only method to clean the node up.

We're also running dpci. (On 3COM503 boards, and thru a serial line)
We a user kills his PC, the DPCI-sever detects that because it somehow
tests the client once in a while. At least our logfile (/usr/adm/dpci_error_log)
tells me so. Even a blunt reboot after a program hangs does not cause any
processes to run 'wild'.
I must say that remaining processes of this type would cause serious problems
at our sever, since it is already loaded with stuff. A normal user on the
display has at most 20 processes left to use, and then it's out of 
process entries.

Ciao
	Willem Jan Withagen.

Eindhoven University of Technology   DomainName:  wjw@eb.ele.tue.nl    
Digital Systems Group, Room EH 10.10 BITNET: ELEBWJ@HEITUE5.BITNET
P.O. 513                             Tel: +31-40-473401
5600 MB Eindhoven                    The Netherlands