Many thanks to:
Casper Dik <casper@holland.Sun.COM>
John Justin Hough <email@example.com>
Tim Carlson <firstname.lastname@example.org>
My original query was:
>We're running CAP60 (patch level 143) under Solaris 2.3 and there's a
>strange problem. One printer of the ~10 using CAP has stopped
>printing. Jobs sent via a Mac to that printer are fine. Jobs sent via
>Unix (from any machine on the network or from the CAP server) make it
>to the queue, and are reported as "ready and printing," but never
>I can print from Unix with the CAP
> lwpr -p "Laser 10@NYU PHRI"
>command, but not via "lpr -Plaser10".
>I think this was caused by lprm'ing the current job from the queue, but
>the queue is empty, and I can't find any temporary files related to the
>I've stopped and restarted CAP60 and lp services on the server and
>client, with no change. The CAP and printer configs. haven't been
>changed in over a year.
>I've tried making CAP with the latest patches, but I'm getting
>complaints that two include files can't be found:
> /usr/include/netdb.h:66: sys/bitypes.h: No such file or directory
> /usr/include/netdb.h:68: sys/cdefs.h: No such file or directory
>Finally, we've had a persistent problem where all our printers will
>one-by-one start reporting "exec exit failure" and stop printing.
>Stopping and re-starting both lp services and CAP cures this fault.
>I'm hoping that the later patches to CAP will fix this.
Casper got the compilation problem solved on the first try:
=> From: Casper Dik <casper@holland.Sun.COM>
=> You've installed bind 4.9.3 and have been foolish enough to do
=> "make install". SHame on you.
=> Bind's make install destroys /usr/include/netdb.h (it replaces it with
=> its own, not Solaris compatible version).
=> Just get the Solaris 2.x version from another machine and next time watch
=> before you do "make install"
The other suggestions were to build the newest version of
CAP and to check the /etc/cap.printers file for changes or
typos, and to check the spool directory permissions.
I've built and installed the new version of cap, and it
seems to work fine. I couldn't find anything wrong with
the cap configuration. I was able to define a new printer,
directed to the same Appletalk device that the Unix printer
"laser10" was unable to print to. The new printer worked
I finally rebooted the server, and the original "laser10"
destination is working. I suspect some kind of lock got left
behind when I lprm'ed the "active and printing" file from a
Mark Bergman email@example.com
System and Network Administrator 212-578-0822
Public Health Research Institute Rm. 1074, 455 1st Ave, NY NY, 10016
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:57 CDT