You are not logged in.
Hi all,
My college has a CUPS 1.5.7 print server (that of course I can't modify) and before the upgrade of my computers to CUPS 2.0, I had the following:
~/.cups/client.conf
ServerName 127.0.0.1:42631
Where 127.0.0.1:42631 was a point to point connection, using SSH from my computer to the print server, going through the only machine in school that can speak both with the outside world and the print server.
That used to work.
Now, it only works if I specify this ServerName in /etc/cups/client.conf (sorry for bold, there is no inline code markers AFAIK); however, 2 issues:
This is ugly
client.conf(5) will be deprecated soon
What should I do now? (Except using the school's computer to print because, well, this is no fun).
What i know is: the print server uses CUPS and ddns. However, there is no way I can put my computer on the same networks the print server is and I would highly prefer not having to write a line per printer in the school (there already is someone taking care of that, it's pointless to re-do what's already there).
Last edited by Moviuro (2014-11-25 07:42:45)
bspwm, BTRFS over LUKS
Archlinux a lot, FreeBSD more and more...
Murphy's rule: The day you need a backup, you tell yourself you should have created some.
Offline
There is an upstream cups bug relating to ~/.cups/client.conf and the ServerName directive at...
https://www.cups.org/str.php?L4528
Regards
Paul.
Offline
There is an upstream cups bug relating to ~/.cups/client.conf and the ServerName directive at...
Oh, thanks.
But on the other hand, slowly deprecating client.conf could make sense as it is clearly stated in client.conf(5) that it will disappear...
I'm a bit reassured, but then... what about next versions?...
bspwm, BTRFS over LUKS
Archlinux a lot, FreeBSD more and more...
Murphy's rule: The day you need a backup, you tell yourself you should have created some.
Offline
I'm also wondering what is going to happen in newer versions of cups when client.conf is eventually deprecated as shown at...
https://www.cups.org/documentation.php/ … .conf.html
I've not been able to find anything out, so if anyone else knows, please post!
Last edited by paulkerry (2014-11-28 19:47:06)
Offline
Okay, so I just upgraded (finally!) to 2.0.2 and client.conf seems to be read and bug has been fixed.
bspwm, BTRFS over LUKS
Archlinux a lot, FreeBSD more and more...
Murphy's rule: The day you need a backup, you tell yourself you should have created some.
Offline