On 2019-03-01, mick crane <mick.cr...@gmail.com> wrote: > On 2019-02-28 18:59, mick crane wrote: >> hello >> is buster >> I can print from command line with >> "lp filename" >> but not with "lpr filename" >> when printing from terminal the font is a bit big and uses too much >> paper. >> apparently "enscript -FCourier10 filename" for example is supposed to >> work but that sends it to lpr which doesn't. >> Can try to get lpr to work as I have in the past or try to get >> enscript to use lp >> Or maybe there is another way to change printed font size from terminal >> ?
I believe the lpr that works with cups is the one provided by cups-bsd. the -d and -P flags for enscript should be followed by a printer name, not by a file name, according to the man page. enscript -P HP_LaserJet_4000_Series foo.txt > I'm not really understanding. > Is "lp" to do with CUPS and "lpr" to do with lpd daemon ? > I have CUPS server on other PC. > > on client PC > $ lpstat -t > scheduler is running > system default destination: HP_LaserJet_4000_Series > device for HP_LaserJet_4000_Series: socket://10.0.0.108 > > "lp filename" prints OK > > "systemctl start lpd.service" > > "lpr filename" (nothing happens) > > "enscript filename" > [ 1 page * 1 copy ] sent to printer > (but nothing happens) > > enscript filename | lp > [ 1 page * 1 copy ] sent to printer > lp: No file in print request. > > $ enscript -d filename > lpr: test: unknown printer > > $ enscript -P filename > lpr: test: unknown printer > > Do I need to put some sensible values in /etc/printcap to have enscript > working as at the moment /etc/printcap seems to be defining a local > printer ? > Or is there some way to tell any printer requests should go to CUPS > server ? > -- “Let us again pretend that life is a solid substance, shaped like a globe, which we turn about in our fingers. Let us pretend that we can make out a plain and logical story, so that when one matter is despatched--love for instance-- we go on, in an orderly manner, to the next.” - Virginia Woolf, The Waves
