This is Printing-problems-in-v0.9 in view mode; [Up]
Date: Sun 07-Jul-1989 17:46:54 From: Unknown Subject: Printing problems in v0.9 We are having problems printing. I checked with ps and npd is up. lpc, lpq and the NeXT printer application are of no help. Enabling and disabling and reseting from the printer application does not help, and niether does doing the same thing from lpc. The logs say, Jul 7 12:15:41 next npcomm[358]: couldn't create public context Jul 7 12:15:42 next npcomm[358]: problem creating PS print context Jul 7 12:16:54 next lpd[363]: /usr/adm/np-log: No such file or directory Jul 7 12:16:56 next npcomm[364]: couldn't create public context Jul 7 12:16:56 next npcomm[364]: problem creating PS print context Jul 7 12:18:50 next lpd[382]: /usr/adm/np-log: No such file or directory Jul 7 12:18:51 next npcomm[383]: couldn't create public context Jul 7 12:18:51 next npcomm[383]: problem creating PS print context Jul 7 12:29:57 next npcomm[433]: couldn't create public context Jul 7 12:29:57 next npcomm[433]: problem creating PS print context Does anyone know what the problem is? >From: jacob@gore.com (Jacob Gore)
Date: Sun 08-Jul-1989 03:26:14 From: Unknown Subject: Re: Printing problems in v0.9 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 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!
Date: Sun 11-Jul-1989 16:44:28 From: Unknown Subject: Re: Printing problems in v0.9 Thanks to ric@arizona.edu and dml@esl.uucp for helping me solve my printing Jul 7 12:15:41 next npcomm[358]: couldn't create public context Jul 7 12:15:42 next npcomm[358]: problem creating PS print context I solved the problem by running the following from root, for i in /* list of the 40 or so userids on our NeXT */ do echo dwrite PublicWindowServer Yes | su -f $i echo $i fixed done Unfortunately, now I am encountering a new printing problem, Jul 10 12:45:13 next npcomm[550]: found mismatch on printer status, 0x00001110 != 0x00000010 Jul 10 12:46:08 next vmunix: Jul 10 12:45:13 next npcomm[550]: found mismatch on printer status, 0x00001110 != 0x00000010 Jul 10 14:26:17 next syslog: Workspace: Open of /dev/tty failed (No such device or address) Jul 10 14:27:13 next vmunix: Jul 10 14:26:17 next syslog: Workspace: Open of /dev/tty failed (No such device or address) Jul 10 14:33:08 next npd[595]: 10000 PrintIt failed Jul 10 14:35:06 next last message repeated 14 times Jul 10 14:35:13 next npd[595]: 10000 PrintIt failed Jul 10 14:36:15 next last message repeated 5 times Jul 10 14:36:58 next npd[595]: 10001 PrintIt failed Jul 10 14:37:39 next npd[595]: 10001 PrintIt failed Jul 10 14:48:11 next npd[595]: 10001 PrintIt failed Jul 10 14:52:59 next npd[595]: 10001 PrintIt failed Jul 10 14:54:33 next last message repeated 3 times Jul 10 14:55:40 next npd[595]: 10001 PrintIt failed >From: kean@mist.CS.ORST.EDU (Kean Stump)
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.