Print Utility for UNIX 1.8 FAQ --------------------------------------------------------------------------- Q1: How can I determine which printing system is in use on my system? A1: Probably the easiest way is to use rpm: # rpm -q LPRng If aren't using rpm and you have "strings", you can examine the lpd executable: # strings /usr/sbin/lpd | grep LPRng You can also look in /etc for a lpd.conf file which would indicate LPRng, and also if the lpr executable is a symbolic link, that would also indicate LPRng. Q2: When I try to install the rpm, it fails the dependency check. What do I do? A2: The normal distributions of "Print Utility for Unix" for linux depend on the shared c runtime library libc.so.6 aka glibc2. As rpm uses it's own database for dependency checking, it may or may not be accurate. So the first step is to determine whether it is really available or not. If it is available, you can install the rpm with the --nodeps option. If it is not available, you can either install it or use the statically linked version of "Print Utility for Unix". To determine whether libc.so.6 is available on your system, look for libc.so.6 in the trusted system library areas. ls /lib/libc* /usr/lib/libc* Q3: When I try to add the printcap entry, it complains about lpd_bounce and I can't print. A3: This is due to running an older version of LPRng. lpd_bounce was introduced in version 3.6.1 of LPRng in March 1999. If you can't upgrade to a newer version, you can change the printcap entry to look like: :\ :bq=@:\ :lp=:\ :sd=/var/spool/lpd/:\ :mx#0:\ :sh:\ :if=/usr/lib/kmpu/printutility.filter: where: printer - name of the local print queue you are creating hostname - the printer host name port - the printer's port, generally print Q4: My distribution is not listed. Can I use one of the others? A4: Please contact KONICA MINOLTA BUSINESS TECHNOLOGIES service person. Q5: Should I use the "dynamically linked" or "statically linked" installation kit? A5: The dynamically linked kit contains executables that depend on glibc2, which most modern distributions have installed by default. It is much smaller. The statically linked kit contained executables that are standalone and do not depend on glibc. The binaries are much larger. If you have glibc2, use the dynamically linked kit. Q6: Can I set up the print queues without using "kpappendprinter"? A6: No, if you use CUPS spooler. Yes, if you use lpr or LPRng spooler. The information you need is provided in the readme.txt file. Q7: Do you support other spoolers? A7: No, not at this time. Q8: When I try to use a "kpalias" printer under Linux LPRng systems, I get the following error: "Fatal error - Maximum of 1 copies allowed" and my job will not print. What should I do? A8: You will only see this problem if you configured the "kpalias" printer to print more than one copy. This is a problem with LPRng based print spoolers only. "kpappendprinter" creates a very basic printer description in the /etc/printcap (or in the of RedHat Linux 7.1 and above, /etc/printcap.local) file. This basic printer description does NOT contain the "maximum copies" directive, as a result, LPRng defaults to a maximum copy = 1. To fix this, you need to add ":mc=0:\" to this kpprinter's printer description. LPRng interprets the maximum copy limit equal to zero as "unlimited". An example "Print Utility for UNIX" printer's printcap entry is given below: :\ :rm=:\ :rp=print:\ :lpd_bounce:\ :sd=/var/spool/lpd/:\ :mx#0:\ :mc=0:\ :sh:\ :if=/usr/lib/kmpu/printutility.filter: Q9: I fixed #8 by adding ":mc=0:\" to the /etc/printcap description, but now when I try to print using that "kpalias" printer nothing prints out. There are no error messages generated, what am I doing wrong now? A9: If you are seeing this problem (no output generated) then you must have used "kpalias" to save a script that keeps all of the printer defaults, with the possible exception of the number of copies to generate. When "kpalias" generates the executable "kpalias" printer script, it uses the standard lp command for number of copies "-n X", where X = the number of copies you want printed. Even if you leave the default copies as one, the "kpalias" executable script contains the following: lp -d kpprintername -n 1 $* <- where $* represents the passed to it Because this command line structure does not pass any options to the printutility.filter, the printutility.filter is not executed and the job does not print. To fix this problem, simply change the "-n 1" to "-ocopies=1" and the job will print. So if you have a "kpalias" created printer called duplex_3copies, you must edit the "duplex_3copies" script from: lp -d -n 3 -oDuplex=DuplexNoTumble $* to: lp -d -ocopies=3 -oDuplex=DuplexNoTumble $* Q10: After using "kpp" to print within Netscape Navigator I notice a lot of temporary files called "kp.XXXXS" where XXXXS = random characters? What are these files and is it safe to delete them? A10: Yes, it is safe to delete them. "kpp" needs to spool the X-Window application's print output to a temporary file called "kp.XXXXX" before it passes it to the "kp" executable. Unfortunately, after "kp" finishes processing the job, "kpp" does not go back and delete the temporary file. For now, it is safe to delete all "kp.XXXXX" files by simply typing "rm -F kp.*" to get rid of these temporary files Q11: When I run "kpconfig -d" a segment fault is generated and a file called "kpconfig.XXXXX" is created in the directory that I ran "kpconfig" from. Is this normal? A11: No! However, the segmentation fault occurs after "kpconfig" completes its job. For now, simply delete the "kpconfig.XXXXX" temporary file. This will be fixed in a later version of "Print Utility for Unix".