If you run 'strings /usr/openwin/bin/Xprt | grep lpget' you'll see the command it
runs to find printers - if you run that yourself, does it give a list of printers?

Alan Coopersmith wrote:
> If you run 'strings /usr/openwin/bin/Xprt | grep lpget' you'll see the command
> it runs to find printers - if you run that yourself, does it give a list of 
> printers?

No, "lpget" only generates an error:
-- snip --
% strings /usr/openwin/bin/Xprt | fgrep lpget
LANG=C lpget -k description `lpstat -v | nawk '$2 == "for" { x = match($3, /:/);
print substr($3, 1,x-1) }' | sort` | nawk -F: ' NF == 2 { name=$1 }  NF == 1 {
sub("^.*description\( - undefined|=\)","");  printf "%s\t%s\n",  name, $1 } '

% LANG=C lpget -k description `lpstat -v | nawk '$2 == "for" { x = match($3,
/:/); print substr($3, 1,x-1) }' | sort` | nawk -F: ' NF == 2 { name=$1 }  NF ==
1 { sub("^.*description\( - undefined|=\)","");  printf "%s\t%s\n",  name, $1 }
'
Usage: lpget [-k key] [list|(printer) ...]
-- snip --

But I don't have any print queues defined - that's the simple problem. Adding a
print queue to the spooler makes "lpget" happy.
My fault.

Either we can close this bug as INVALID ("user too dumb" =:-) or adjust the
buildin script a little that it generates less confusing output... :)

Long term I'd like to delete the script completely and switch over to PAPI so 
that we're not so reliant on lp command output format and such a complex bit
of shell hackery (which in a weak moment I may admit some guilt in creating).

Unfortunately, that has to wait both for PAPI integration to Solaris, and someone
having time to rewrite BuildPrinterDb/AugmentPrinterDB to use PAPI.

*** This bug has been marked as a duplicate of 411 ***