[snip] On 5/2/2015 3:22 PM, Johan Kragsterman wrote: > Here's how it looks like in my fat clients filesystem: > > admin@ws0:/etc/cups$ ls > cups-browsed.conf ppd raw.types subscriptions.conf.O > cupsd.conf printers.conf snmp.conf > cups-files.conf printers.conf.O ssl > interfaces raw.convs subscriptions.conf > admin@ws0:/etc/cups$ > > > As you can see, I got all the normal cups files there, I don't know if there > is a different with the ltsp-pnp. I didn't build my chroot's with any special > options. > > As you also can see, I got both printers.conf and printers.conf.0. The > latter is the one that cups is building automatically, and it is named like > that, because the printers.conf already exists. > > Here's my cups-browsed.conf: > > admin@ws0:/etc/cups$ cat cups-browsed.conf > # Which protocols will we use to discover printers on the network? > # Can use DNSSD and/or CUPS, or 'none' for neither. > BrowseRemoteProtocols dnssd cups > > # Which protocols will we use to broadcast shared local printers to the > network? > # Can use DNSSD and/or CUPS, or 'none' for neither. > # Only CUPS is actually supported, as DNSSD is done by CUPS itself (we ignore > # DNSSD in this directive). > # BrowseLocalProtocols none > > # Settings of this directive apply to both BrowseRemoteProtocols and > # BrowseLocalProtocols. > # Can use DNSSD and/or CUPS, or 'none' for neither. > BrowseProtocols dnssd cups > > # Only browse remote printers from selected servers > # BrowseAllow cups.example.com > BrowseAllow 192.168.10.250 > BrowseAllow 192.168.10.0/24 > BrowseAllow 192.168.10.0/255.255.255.0 > > # Use BrowsePoll to poll a particular CUPS server > BrowsePoll 192.168.10.250:631 > BrowsePoll 192.168.10.250 > # BrowsePoll cups.example.com:631/version=1.1 > > # Use DomainSocket to access the local CUPS daemon via another than the > # default domain socket > # DomainSocket /var/run/cups/cups.sock > > # Set CreateIPPPrinterQueues to "Yes" to let cups-browsed discover IPP > # network printers (native printers, not CUPS queues) with known page > # description languages (PWG Raster, PDF, PostScript, PCL XL, PCL > # 5c/e) in the local network and auto-create PPD-less print queues for > # them (using a System V interface script to control the filter > # chain). Clients have to IPP-poll the capabilities of the printer and > # send option settings as standard IPP attributes. We do not poll the > # capabilities by ourselves to not wake up the printer from > # power-saving mode when creating the queues. Jobs have to be sent in > # PDF format. Other formats are not accepted. This functionality is > # primarily for mobile devices running CUPS to not need a printer > # setup tool nor a collection of printer drivers and PPDs. > > CreateIPPPrinterQueues Yes > > # The AutoShutdown directive specifies whether cups-browsed should > # automatically terminate when it has no local raw queues set up > # pointing to any discovered remote printers (auto shutdown > # mode). Setting it to "On" activates the auto-shutdown mode, setting > # it to "Off" deactiivates it (the default). The special mode "avahi" > # turns auto shutdown off while avahi-daemon is running and on when > # avahi-daemon stops. This allows running cups-browsed on-demand when > # avahi-daemon is run on-demand. > > # AutoShutdown Off > # AutoShutdown On > # AutoShutdown avahi > > # The AutoShutdownTimeout directive specifies after how many seconds > # without local raw queues set up pointing to any discovered remote > # printers cups-browsed should actually shut down in auto shutdown > # mode. Default is 30 seconds, 0 means immediate shutdown. > > # AutoShutdownTimeout 30 > > # Unknown directives are ignored, also unknown values. > admin@ws0:/etc/cups$ > > > > > And here's my printers.conf: > > admin@ws0:/etc/cups$ sudo cat printers.conf > [sudo] password for admin: > # Printer configuration file for CUPS v1.7.2 > # Written by cupsd > # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING > <Printer HP-Color-LaserJet-CP4520-Series> > UUID urn:uuid:21be3120-0f61-3fa8-7d7d-7129f1350fab > Info HP Color LaserJet CP4520 Series [90D6CD] > Location print > DeviceURI ipp://print.local:631/print > PPDTimeStamp * > State Idle > StateTime 1430565618 > Type 4 > Accepting Yes > Shared No > ColorManaged Yes > JobSheets none none > QuotaPeriod 0 > PageLimit 0 > KLimit 0 > OpPolicy default > ErrorPolicy retry-job > Option cups-browsed true > </Printer> > admin@ws0:/etc/cups$ > > > > I got this file through first editing cups-browsed, so that I could configure > the exact printer I wanted, and then copy the file from my running fat > client, and putting it into the chroot(and of coarse rebuilding the image). > You will also need a root user in the fat client image. > > > Regards Johan > > > Neither the server nor the image has an existing cups-browsed.conf, > though from the manpage it seems that it may not be necessary. If I > understand it correctly, there are defaults for the values that probably > allow things to just work in many/most circumstances. > > Is there a how-to for setting up server-connected printers for fat > clients, or can someone explain how? > >
@ Johan: Thanks for detailing that, but we may be dealing with a difference between ltsp-pnp and the ltsp non-pnp that you use. I'm finding that ltsp-pnp strips the configuration from printers.conf with every image update, so I don't see how your method will work for me. But I did some further reading, including https://sourceforge.net/p/ltsp/mailman/ltsp-discuss/thread/1310159742.1892.4.camel@alkis/ https://www.cups.org/documentation.php/doc-1.7/sharing.html?VERSION=1.7&Q= https://www.cups.org/documentation.php/doc-1.7/man-client.conf.html?VERSION=1.7&Q= For some reason I can create an /etc/cups/client.conf that is included in the image (I double-checked by mounting the image) but is not in the filesystem loaded on the fat client. Leaving that mystery for later research, I worked around it by creating ~/.cups/client.conf, and if I add this sole line to it (plus an EOL character), the server-connected printer is automatically available for the fat client: ServerName 192.168.1.8 Great! But I'm using DHCP for the server IP address for the sake of easy deployment, so I would like to use the hostname option for ServerName instead of the IP address option. So I tried (to provide a specific example): ServerName Dell-Lubuntu This fails. It seems that by "hostname" they mean fully-qualified domain name, as in the examples from the older documentation: https://www.cups.org/documentation.php/doc-1.5/ref-client-conf.html On the LAN, does anyone know how a hostname can be specified as a FQDN? (I'll also note that in one of the above links, Alkis suggested trying just "ServerName server" but that failed for me.) ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
