The Red Hat printer configuration tool does not allow a printer alias to be defined. This should be possible either using an additional text field or at least by providing the queue name in the usual printer(|alias)* format.
I'm not actually sure that cups provides that facility.
*** Bug 97422 has been marked as a duplicate of this bug. ***
Yes, you are right, I could not find this either in cups. So I guess there are two solutions: 1) Warn the user about it and remove the alias 2) For each alias set up a new queue which spool to the original one Probably 1) is better.
Its a bit of a shame, really. Looking at the generated printers.conf file, it is easy to imagine added a field named 'aliases' for each defined printer and then allowing config tools to plonk alternate names in this field. I took a quick look through the source code to see how miserable a change this would be.. well, there are lots of subsystems that would need changes. But the code seems pretty clean, and is easy to understand..
*** Bug 107849 has been marked as a duplicate of this bug. ***
This bug also exists in RHEL3 RHEL3 will allow you to add aliases - however they will not work. not exactly the behaviour i'd expect from a "enterprise" system. any idea if fixing this (so aliases work) is likely to be done for RHEl3
Found this useful item via google: ------------------------------------------------------------------ Re: cups printer aliases * From: Ian Mortimer <ian physics uq edu au> * To: fedora-list redhat com * Subject: Re: cups printer aliases * Date: Tue, 23 Dec 2003 14:09:35 +1000 > Anyone know if there any sign of cups supporting printer aliases in the > near future? > > I have come across: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=91674 > > which seems to indicate a glimmer of hope. There's a trick you can use: create a printer class with the alias name and add the printer to the class. -- Ian ------------------------------------------------------------------ Now to see if I can create classes via RH config utils.
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.