Xref: utzoo comp.unix.questions:6829 comp.unix.wizards:8202 comp.unix.microport:579
Path: utzoo!mnetor!uunet!husc6!uwvax!geowhiz!uwspan!root
From: root@uwspan.UUCP (Sue Peru Sr.)
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.unix.microport
Subject: Re: Trouble killing processes in SysV/AT
Message-ID: <3657@uwspan.UUCP>
Date: 2 May 88 20:41:23 GMT
References: <3950@killer.UUCP> <3951@killer.UUCP> <3281@pbhyf.PacBell.COM>
Reply-To: root@uwspan.UUCP (Sue Peru Sr.)
Followup-To: comp.unix.questions
Organization: U of Wisconsin - Madison  Spanish Department
Lines: 63

+---- Wolf Paul writes in <3951@killer.UUCP> 
| Can anyone enlighten me as to what causes a process to become "immortal"
| in System VR2,  or Microport UNIX System V/AT, to be more specific?
+----

Microport users out there with the BETA everex tape driver try this:

	find . -print | cpio -ocv | strm -o /dev/rmt0

	with a WRITE PROTECTED tape!

	after the cpio starts spitting out the filenames, strm will
	hang (because of the R/O tape).  You can kill the find, the cpio,
	but not the strm!  Not only can't you kill it, you can't even
	start up another one cuz it has not released  /dev/rmt0.

	I'd like some more info on this before I bother Microport with it -
	is it just me?... :-)

While I'm at it, would y'all send me any lists of bugs you have found - I'd
like to compile a "user" buglist to contrast with the Microport supplied one...

	(mail to plocher@puff.cs.wisc.edu - this is the most reliable mail
	 site I have access to - Internet, uucp, cs-net, and bitnet mail
	 all can find this spot...)

  -John Plocher

	    ---- ...This bears repeating from time to time... ----

These are the automatic mailings avaliable to you.  To have one mailed
to you automatically, send a mail message to

			    microport@uwspan.uucp
				   -or-
		      ...!uwvax!geowhiz!uwspan!microport

with the the subject described below.

The Subject: field should be	What will get mailed back to you	Size
----------------------------	--------------------------------	----
"Subject: send info"		Introduction and newsgroup guidelines   (~ 7K)
"Subject: send buglist"		"Up to date" lists of all reported bugs	(~20K)
				( Last modified Feb 1988 )
"Subject: send version"		Modification dates of the above lists	(~ 1K)

If you already have a copy of the bug lists, you should request the version
message to see if you really need a new copy of the bug lists.  (note the
size difference!)

i.e.:  To get a message containing the times that the buglists were last
       updated you need to send a message like this:

	% mail microport@uwspan.uucp
	Subject: Please send the version list
	Thanks
	^D
	%

The body of the message ("Thanks") is ignored.

-- 
Comp.Unix.Microport is now unmoderated!  Use at your own risk :-)