Article View: comp.sys.next.sysadmin
Article #1546Atalkd
From: Steve Spicklemire
Date: Fri, 16 Oct 1992 05:45
Date: Fri, 16 Oct 1992 05:45
28 lines
1333 bytes
1333 bytes
Hi again, I've been experimenting with atalkd a bit more to see what conditions seem to make it break, and there does seem to be a fairly clear pattern. If I'm the only one in the building (i.e., no-one else is printing, or really using the network) I can print to my heart's content as long as nothing 'bad' happens (e.g., the printer runs out of paper, ouch! -> zombie land). If other folks are printing and the NeXT has to 'wait in AppleTalk line', it's generally bad news. Anyway, I haven't heard any fixes yet for this, but at least now I know that it helps to 1) check for plent of paper first and 2) wait for everyone else to go home! :-(. BTW, other than this *one* problem, I'm *really* liking 3.0. Of course I've never had a 24M station before, bit I'll take a 24M 3.0station over an 8M 2.1 station *any* day. :-) cheers, -steve -- Steve Spicklemire steves@truevision.com (daily) spicklemire@gandlf.uindy.edu (NeXTmail!) Dept. of Mathematics and Physics, Univ of Indianapolis (317) 788-3313
Technical Details
Message-ID:
<1992Oct16.054526.15051@truevision.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!epicb!stevesShow Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.sysadmin Path: arc1-ca.pugleaf.net!sparky!uunet!epicb!steves From: steves@truevision.com (Steve Spicklemire) Subject: Atalkd Message-ID: <1992Oct16.054526.15051@truevision.com> Organization: Truevision Inc., Indianapolis, IN Date: Fri, 16 Oct 1992 05:45:26 GMT Lines: 28