Hmmm... I don't think I replied to this. OK. Have you looked at the files in the samba spool (/var/tmp) to see if they contain an extra page or is the extra page being added by lprng?
Second question, do you want to learn about print filters? I have attached a
postscript file which is a tutorial on print filters. After you have read this,
and play with it, you should have much more insight into this sort of
problem. Printer problems will always be with you, so this information is
good to know.
Joel
On Fri, May 31, 2002 at 03:45:17PM -0700, Brian W. Carver wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Joel,
>
> You are right to feel that I don't understand any of this. I think your
> assumptions are probably on target. I especially like your idea that
> samba is to blame for this, as that would seem to explain (to me) why
> this is a client only issue. I tried adding :sh: to printcap and lpd
> complained and insisted on ff_separator. I tried printing anyway, and
> the same problem exists.
>
> Here is the smb.conf file. I don't see what to do here, but perhaps you
> or someone else will! Thanks!
>
> # Samba config file created using SWAT
> # from localhost (127.0.0.1)
> # Date: 2002/05/01 04:43:18
>
> # Global parameters
> [global]
> interfaces = 192.168.0.1/24 127.0.0.1/24
> bind interfaces only = Yes
> security = SHARE
> encrypt passwords = Yes
> map to guest = Bad User
> log file = /var/log/samba/log.%m
> time server = Yes
> socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
> character set = ISO8859-15
> os level = 2
> dns proxy = No
> wins support = Yes
> guest account = smbuser
> hosts allow = [snipped]
> printing = lprng
> hide dot files = No
> veto files = /*.eml/*.nws/riched20.dll/*.{*}/
>
> [printers]
> comment = All Printers
> path = /var/tmp
> create mask = 0600
> guest ok = Yes
> printable = Yes
>
> [printer1]
> path = /var/tmp
> read only = No
> create mask = 0600
> guest ok = Yes
> printable = Yes
> printer name = printer1
> oplocks = No
>
>
> Joel Hammer wrote:
> | 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
>
> - --
> 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
>
> iD8DBQE89/z8ATQSaAIcWwsRAlRvAJ91QIfGGYz/EKxGTiCOmO36PGv8XACeJXwU
> Fji6IQvGbn+79EGrMmgbW08=
> =3Ljd
> -----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.
> -----------------------------------------------------------------------------
Filters.ps
Description: PostScript document
