Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!versatc!leadsv!esl!dml
From: dml@esl.UUCP (Denis Lynch)
Newsgroups: comp.sys.next
Subject: Re: Printing problems in v0.9
Message-ID: <935@esl.UUCP>
Date: 8 Jul 89 03:26:14 GMT
References: <1989Jul7.130806.9545@gpu.utcs.utoronto.ca>
Reply-To: dml@esl.UUCP (Denis Lynch)
Organization: ESL, Inc., Sunnyvale, CA.
Lines: 23

In article <1989Jul7.130806.9545@gpu.utcs.utoronto.ca> nishri@gpu.utcs.utoronto.ca (Alex Nishri) writes:
>We are having problems printing.

>The logs say,
>   Jul  7 12:15:41 next npcomm[358]: couldn't create public context

This sound like the dreaded Public Context problem. If it is, here's what
happened: Someone doesn't have Public Window Server set in there "cube"
preference. They printed something, causing npd to create its print context
as a private context owned by that user's job. Once that user logged out,
nobody else could access that context. Thus npd wouldn't work any more.

The solution is to make sure that all your users set Public Window Server.
In the meantime, reboot your machine and all should be well.

If not, I'll be curios to here what the cause *really* is!


-- 
Denis Lynch                          
ESL Incorporated                         decwrl!borealis!\
ARPA: dml%esl.ESL.COM@ames.arc.nasa.gov    ucbcad!ucbvax!- ames!- esl!dml
SMAIL: dml@esl.ESL.COM                                  lll-lcc!/