Cups importing/exporting

[Dustin]

Well I thank you both for for your replies and today I plan on starting in on this.  I am going to just go for it and see what I come up with.  I realyl like both of your points and you are right, anytime you are upgrading it is different for each user and does take some manual intervention.  Thanks once again for your help





> > > So, have a test CUPS 1.2 server running, create one printer queue from
> > > a CUPS 1.1 server, compare their config file and look at the differences
> > > and work from there.
> >
> > Isn't that overly complicated (and error prone)?
> >
> > Isn't it simpler (and more reliable) is to run the "lpadmin" command for each printer (with the right parameters which you can derive from "lpstat -v" [and "lpstat -l -p" if you require to know the "Description" and "Location" and "Banner" and .... fields]. That's also easily scriptable...
> >
> > The lpadmin command will automatically create the correct printers.conf entries.
> >
> If not careful, there sure to be some errors. But it worked for me. An
> with varying environments, it's certain the process of upgrading will
> be different for everyone.
>
> What you have described is part of my conversion process which creates
> the script that uses the lpadmin commands with the appropriate
> parameters and then executing that script into a running CUPS 1.2 server
> which in turn creates the printers.conf file. That 1.2 printers.conf
> file, and other supporting files, is then used to replicate additional
> servers.
>
> The bottom lines is there is no straight upgrade process without manual
> intervention of something. And I think that's what Dustin was trying to
> figure out.
>
>
> Thanks,
> Angel