Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!arnold!dave
From: dave@arnold.UUCP (Dave Arnold)
Newsgroups: comp.sys.att
Subject: OBM problems
Message-ID: <150@arnold.UUCP>
Date: Wed, 2-Sep-87 21:42:24 EDT
Article-I.D.: arnold.150
Posted: Wed Sep  2 21:42:24 1987
Date-Received: Sat, 5-Sep-87 07:35:51 EDT
Organization: Mission Viejo, Ca
Lines: 50
Keywords: uucp crash OBM

I'm having serious problems with my UNIXpc communications, and was wondering
if anybody can offer some advise.  First, a little background:

I was told by an AT&T hotliner that I should have my data line on
/dev/ph1, so my L.sys file has all uucp connections made on ph1,
and all my office administration has ph1 set as a data line, ph0
nothing (I only have one line connected to the back of UNIXpc, and
it's on line 2).

And here's a summary of my crash problem, HELP!:

1.	"uucico -r1" executed by cron (smgr) @ 2:00am
2.	Woke up @ 7:00am, went to check mail and news,
	uucico still running (apparently hung), /usr/spool/uucp/LOGFILE
	says OK (conversation complete), setgetty also running (apparently
	hung).
	NOTE: I did "ls -l /dev/ph1" and the group was set to "mail", /dev/ph0
	is set to "sys".
3.	kill -9 uucico, and kill -9 setgetty
4.	uuxqt never ran, so I did a uuxqt manually to process uucp work.
5.	setgetty ph1 1.  Went to work, tried to call 7300 from work, and test
	my uemacs tam library changes, but 7300 would not answer phone.
6.	Arrived home, tried to call some systems using "cu -s1200 -l/dev/ph1",
	But it reported "Error opening modem port, bad address, error = 14".
7.	Thought I might be having hardware problems, so I loaded in my
	diagnostic disk, and ran a full test of modem and dialer.  All passed
	wonderfully.
8.	Hmmm (Actually I wasn't thinking that, I can't use that language here!).
9.	I tried going into office and tried resetting stuff in the office, and
	got errors about trying to open ph0?
10.	I went into "Telephone setup", and changed ph0 to the data line, and
	turned off ph1.  I then switched the line on the back from line 2 to
	line 1.  BTW, office automatically changed all my L.sys entries from
	ph1 to ph0.
11.	tried "cu -s1200 -l/dev/ph0".  It works.
12.	uucp works also.
13.	setgetty ph0 1.
14.	Called home from work again, it works!

But /dev/ph1 is broken!!!!  What's going on here?  Hardware?  Software?  Is the
driver for ph1 corrupted?  I check /usr/adm/unix.log and it doesn't show any
problems with any drivers.  If the driver is corrupted, how do I fix it?
Help!  If I lose ph0, I will lose all contact with the world, and won't
be able to bug you folks on the net anymore!

-- 
Name:		Dave Arnold
USmail:		26561 Fresno, Mission Viejo, Ca, 92691 USA
DDD:		Home: +1 714 586 5894, Work: +1 714 999 3482
UUCP:		...!seismo!uunet!arnold!dave