Very Computer

  Over the next 5 months, I will be upgrading the majority of our
400 or so Sun workstations from 4.1.3 to Sol 2.3 (2.4?).  We currently
have about 50 printers in our printcap files.  I'd like a way to
build the printers database information on the clients without needing
to go into each and issue all the commands over and over.

  I've spent some time in our test machines, and discovered how to
manually edit the /etc/lp/Systems file to add the remote printer
server nodes.  I've also discovered that the directory /etc/lp/printers
has a directory for each printer, and that I can create these, and add
printer information in the /etc/lp/printers/<printername>/configuration
file.  Also, I've discovered that the filter information is stored in the
/etc/lp/filter.table file which can be copied around.

  So much for what I know.  If I clone this information to another
machine, I still need to "accept" and "enable" the printer for it
to work.  These commands seem to be modifying the
/var/spool/lp/system/pstatus file, and I've attempted to modify it
manually, but I don't seem to be able to "fool" the system into
having the printer "accepted" and "enabled" without actually
issuing the commands.  I suspect the numbers in the file are date codes
and I've tried "fooling" it, but to no avail.

  The goal of all this is to have a tarfile that can be dumped onto
the client to setup it's printing system.  If I have to do a foreach
through all the queues as part of the setup, so be it, but it'd be
nice just to drop data on and be done.

  Anyone know how to accomplish this?

-cpf

I had written a script to install printers. You need to first
define all your printers in a file and then run the script on each
machine. It takes care of server/client etc. You can get it through
anonymous ftp from ftp.cps.msu.edu. directory is pub/solaris2/lp

- vasu

:   Over the next 5 months, I will be upgrading the majority of our
: 400 or so Sun workstations from 4.1.3 to Sol 2.3 (2.4?).  We currently
: have about 50 printers in our printcap files.  I'd like a way to
: build the printers database information on the clients without needing
: to go into each and issue all the commands over and over.

:   I've spent some time in our test machines, and discovered how to
: manually edit the /etc/lp/Systems file to add the remote printer
: server nodes.  I've also discovered that the directory /etc/lp/printers
: has a directory for each printer, and that I can create these, and add
: printer information in the /etc/lp/printers/<printername>/configuration
: file.  Also, I've discovered that the filter information is stored in the
: /etc/lp/filter.table file which can be copied around.

:   So much for what I know.  If I clone this information to another
: machine, I still need to "accept" and "enable" the printer for it
: to work.  These commands seem to be modifying the
: /var/spool/lp/system/pstatus file, and I've attempted to modify it
: manually, but I don't seem to be able to "fool" the system into
: having the printer "accepted" and "enabled" without actually
: issuing the commands.  I suspect the numbers in the file are date codes
: and I've tried "fooling" it, but to no avail.

:   The goal of all this is to have a tarfile that can be dumped onto
: the client to setup it's printing system.  If I have to do a foreach
: through all the queues as part of the setup, so be it, but it'd be
: nice just to drop data on and be done.

:   Anyone know how to accomplish this?

: -cpf