Scripting HP/jetadmin to CUPS conversion

[Rex Mueller]

the Printer Name?
from the printers.conf points to the PPD?

so for example My question would be I have "quenames" on my HP/UX box, jet admin initiates a connection to the model script for the printer based on the IP address.
Does CUPS do something similar to probe the device to determine the best model script? OR when you create the printer you need to know the associated model script?

So say for example, in order to create a HP 3800

The command line reference I found is as follows:

/usr/sbin/lpadmin -p name -E -v device-uri -m ppd-filename ENTER

In this line there is variable information for
- name
- device-uri
- ppd-filename

In my prefer script is takes the existing quename "arladmhp5si" and creates and entry in the printers.conf as below:

<Printer alradmhp5si>
Info Created by root
DeviceURI socket://<maskedipaddress>:9100
Location
State Idle
Accepting Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
</Printer>

But it does not execute LPADMIN to associate -m modelfile with the physical device, is only passes the quename as printer and socket://<ipaddress> as DeviceURI.

I am assuming I still need to some how pass the

lpinfo -m |grep LaserJet |awk -F':' '{print $2}' |awk -F' ' '{print $1}' |grep 3800

/usr/sbin/lpadmin -p arladmhp5si -E -v socket://<ipaddress>:9100 -m HP-LaserJet_5Si-hpijs.ppd
ENTER

To make this device available, is my logic flawed or am I heading in the right direction?


>
> No, the printer name points to the PPD file.
>
> You don't have to use lpadmin for an initial configuration - just
> generate printers.conf and *then* start cupsd.
>
> If you want to update printers.conf when cupsd is running, you need
> to use lpadmin...
>
> --
> ______________________________________________________________________
> Michael R Sweet                        Senior Printing System Engineer
>