Bug#711327: cups-client: the -h option has no effect
On Thu 06 Jun 2013 at 19:29:30 +0200, Vincent Lefevre wrote:
> On 2013-06-06 17:58:38 +0200, Didier 'OdyX' Raboud wrote:
> > What do the following commands give?
> >
> > $ lpstat -H
> > $ lpstat -h localhost -H
> > $ lpstat -h localhost:631 -H
>
> ypig% lpstat -H
> lip-printserver1.lip.ens-lyon.fr:631
> ypig% lpstat -h localhost -H
> lip-printserver1.lip.ens-lyon.fr:631
> ypig% lpstat -h localhost:631 -H
> localhost:631
I get the same. In addition, with cups stopped and no CUPS_SERVER
environment variable and with or without a client.conf
root@cups1:~# lpstat -H
localhost:631
lpstat: Transport endpoint is not connected
root@cups1:~# lpstat -h 192.168.7.20 -H
localhost:631
lpstat: Transport endpoint is not connected
root@cups1:~# lpstat -h 192.168.7.20:631 -H
192.168.7.20:631
'Transport endpoint is not connected' comes from getpeername, I believe.
Without a client.conf, cups stopped and CUPS_SERVER set:
root@cups1:~# lpstat -H
192.168.7.20:631
root@cups1:~# lpstat -h 192.168.7.20 -H
192.168.7.20:631
root@cups1:~# lpstat -h 192.168.7.20:631 -H
192.168.7.20:631
I suppose this only serves to back up what Vincent said in his first
post but I hope it might be of use.
Regards,
Brian.
Reply to: