Ok. I get the feeling that you don't really understand print queues and filters. Yes?
I do not see a raw print queue in the two queues you have here in your printcap. I have to assume that all your clients are sending you postscript files and your filter is sending them to your printer unchanged. I assume your printer is a postscript printer. That is, you could just cat a postscript file to it (cat file > /dev/lp0) and it would print it properly. Notice the assumes in this sentence. I do not know anything about your printer filter, /usr/lib/lpdfilter/bin/if. You might want to look at it or send it to me via this list if it is not a binary file. It may contain a clue. As we recall, samba prints for you by: 1. Transferring the print file from the client to a samba spool directory. 2. Invoking lpr, with options, to print the file. Therefore, if samba is causing this problem, there should be a difference in: 1. How the file was transferred to the samba server. The file in the samba spool directory (which will be a postscript file, I assume) and a postscript file generated from the samba server itself when you print to a file. 2. How samba prints the file. The lpr command that samba uses is different from the lpr command you use to print from the server directly. So, the things I would try would include the following: 1. Look at the lpr command in your samba print share. Try using that command, with options that make sense, to print from the samba server command line and see if you get the extra page. For your print file, use a postscript file you generated on the samba server with a print to file option from some application. 2. Remove the rm option in your lpr command in the smb.conf file. Find the print file sent from a client in the samba spool directory, and lpr that file from the command line on the samba server. 3. Try adding :sh: to your printcap definitions. 4. Post your printer share from smb.conf. Joel On Fri, May 31, 2002 at 07:49:45AM -0700, Brian W. Carver wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Extra blank page at end of jobs occurs ONLY when printing from clients > (regardless of their being Win or linux clients). When printing from > Suse server that the printer is attached to, there's no extra form feed. > > When using SuSE to set up printers in 8.0 it chooses lpdfilter by > default. I haven't changed anything about that. > > The HP LJ5L can print at 300dpi or 600dpi and I have two names for the > same printer depending on which dpi I want. "lp" is 300 "printer1" is > 600 and is almost exclusively the one I use. > > My /etc/printcap: > > lp:\ > :cm=lpdfilter drv=upp method=auto color=yes:\ > :lp=/dev/lp0:\ > :sd=/var/spool/lpd/lp:\ > :lf=/var/spool/lpd/lp/log:\ > :af=/var/spool/lpd/lp/acct:\ > :if=/usr/lib/lpdfilter/bin/if:\ > :la@:\ > :tr=:cl:sh: > printer1:\ > :cm=lpdfilter drv=upp method=auto color=yes:\ > :lp=/dev/lp0:\ > :sd=/var/spool/lpd/printer1:\ > :lf=/var/spool/lpd/printer1/log:\ > :af=/var/spool/lpd/printer1/acct:\ > :if=/usr/lib/lpdfilter/bin/if:\ > :la@:\ > :tr=:cl:sh: > :ff_separator=false:\ > > As for why I'm using the ljet4 driver, I couldn't tell you. When setting > up printers with Yast2 in SuSE 8, I just went with the flow and picked > the defaults. Everything works beautifully except for this blasted extra > form feed. As far as I know I might be sending jobs to a raw print queue > from clients, I wouldn't know how to tell. > > I've looked for a solution from the client side, but within Win the > option to not print a page between jobs is not even available (it's > greyed out), and as I said, I get the same problem from linux clients > (also on Suse 8) on the network as well, so that struck me as being more > suggestive of a server-side solution, but I wouldn't know for sure. > > I also found a file called /etc/lpdfilter/HP-escapes that looks > potentially interesting, but I don't understand it. Here it is: > > - --- > This file describes some common escape sequernces for HP DeskJet > printers. They may used in the configuration file > /etc/lpdfilter/<queue>/conf for printer queues for HP DeskJets. > > * Line termination settings > > ~ \033 & k # G > > ~ with the values # > > 0 = CR=CR ; LF=LF ; FF=FF (default, which is DOS ASCII mode) > 1 = CR=CR+LF; LF=LF ; FF=FF > 2 = CR=CR ; LF=CR+LF; FF=CR+FF (to print ASCII files from Linux systems) > 3 = CR=CR+LF; LF=CR+LF; FF=CR+FF > > * The quality setup > > ~ \033 ( s # Q > > ~ with the values # > > 1 = draft = 240cps > 2 = letter = 120cps (default) > > * Text scale mode (ignored in landscape mode) > > ~ \033 & k # W > > ~ with the values # > > 5 = off (default) > 6 = on > > * Perforation skip mode > > ~ \033 & l # L > > ~ with the values # > > 0 = off = 0.0 in Top Margin > 1 = on = 1/2 in Top Margin (default) > > * Left margin > > ~ \033 & a # L > > ~ with the values # = column number > ~ default = 0 = 1/8 in left margin > > * Pitch > > ~ \033 ( s # H > > ~ with the values # = cpi (characters per inch) > ~ default = 10 characters per inch > - --- > > Any help greatly appreciated. Still pulling hair out over here! > > Joel Hammer wrote: > | Describe your printing set up. [snip] > |> > |>HP Laserjet 5L running the ljet4 driver on SuSE Linux 8.0. Printer is > |>attached to this SuSE "server". A client computer on Win 98 connects via > |>samba and can print beautifully. Problem: client prints extra blank page > |>at end of every job. Searched web. Common problem. None of the solutions > |>work, mainly because they mostly talk about editing apsfilter, which I'm > |>not using. Some solutions talk about editing /etc/printcap. First tried > |>:sf:\ but when I restarted lpd it complained I should use > |>:ff_separator:\ false instead. (Tried printing anyway and problem still > |>same.) Now with ff_separator set to false lpd will restart without > |>complaining, but problem persists. Tried SuSE list several times. No one > |>can sovle it. Migraine increases. > |> > |>Who wants to waste paper? Why is this stupid form feed the default? > |>PLEASE help me get rid of it. I really feel I'm losing my mind over this. > > - -- > Brian > Support EFF! http://www.eff.org/ > They're defending YOUR rights online. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQE8942IATQSaAIcWwsRAv5eAKDQalHyaSGk2wzOU8S5O9R8CMVBUgCgjFK2 > bNAKL0dlVvoLat+RFqFRp6k= > =SeJB > -----END PGP SIGNATURE----- > > > ----------------------------------------------------------------------------- > YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST > The address you post from MUST be your subscription address > > If you need help, send email to [EMAIL PROTECTED] (or lprng-requests > or lprng-digest-requests) with the word 'help' in the body. For the impatient, > to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] > with: | example: > subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] > unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] > > If you have major problems, send email to [EMAIL PROTECTED] with the word > LPRNGLIST in the SUBJECT line. > ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
