home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.appletalk
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!henson!reed!horde
- From: horde@reed.edu (Mr. Heiji Horde)
- Subject: Re: Papif (CAP 6.0/126) problems *almost* solved! (Q)
- References: <traurig-190193164639@skydvr.sanders.lockheed.com> <1993Jan20.221240.19026@cam.compserv.utas.edu.au>
- Organization: Twisted Genius Rehabilitation Center, a Division of MHE
- Date: Fri, 22 Jan 1993 00:38:49 GMT
- Message-ID: <1993Jan22.003849.2846@reed.edu>
- Lines: 20
-
- In article <1993Jan20.221240.19026@cam.compserv.utas.edu.au> tgray@mersey.appcomp.utas.edu.au (Tony Gray) writes:
- >I recently installed CAP in a Sparcstation-10 and had printing problems
- >which were reported as "permission denied" on /dev/nit. Rather than
- >changing the protections on /dev/nit, I was told to install papif as an
- >SUID process (owned by root). It works... I doubt that this would
- >help you with your netware spooler problem though.
-
- Yeah, I had a similar problem on my DECs running Ultrix 4.2 with Cap60
- patchlevel 126, configured for ethertalk phase 2. Papif (among several
- other programs) were giving up with the error:
- open: ne0: Permission Denied
- ne0 is the network interface on the machine. Making the offending
- programs setuid root allowed them to work properly.
- Unfortunately, I don't look at having unecessary setuid root programs sitting
- around as being optimal. Does anyone else have a better solution to this?
- I'm not too worried about these programs since I haven't been able to
- hack root using them...yet... ;)
-
- -Heiji (horde@reed.edu)
-
-