[cups.general] CUPS, Kerberos, and ServerName

[Rick Cochran]

Erk.  It works now.  The print queue on the remote server shows up in TextEdit, 
Firefox, and Safari.

The only thing which changed is that I went on vacation, taking my MacBook Pro 
with me.  Always a good idea, but I suspect that the reboot helped.  I doubt 
this is cupsd needing to be HUPed - perhaps an OS component.

When I print from various applications, I get prompted for a Kerberos 
name/password/realm unless I already have an appropriate TGT.  This is very good.

-Rick

Rick Cochran wrote:
> Michael R Sweet wrote:
>> Rick Cochran wrote:
>>> Michael R Sweet wrote:
>>>> All of the Apple GUIs now respect the client.conf file, so a per-user
>>>> ~/.cups/client.conf file can point to the per-user cupsd's domain
>>>> socket, and then everything works as before.
>>>
>>> gibbie> cat ~/.cups/client.conf
>>> ServerName page4.cit.cornell.edu
>>> gibbie> lpstat -a
>>> ansel-k accepting requests since Fri Jul 18 16:09:58 2008
>>> gibbie>
>>>
>>> Print dialog box for Firefox says "No Printer Selected".  In other 
>>> words, the Apple printing system does not seem to know about "ansel-k".
>>
>> Did you start Firefox before you created that file?
> 
> No.  I specifically checked for this possible explanation.
> 
>> If you click on the "No Printer Selected", do you get a list of
>> print queues to choose from?
> 
> No.  Just "No Printer Selected".
> 
>>  > ...
>>> One thing I see in the error log is this:
>>>
>>> Get-Printer-Attributes ipp://localhost/printers/
>>> get_printer_attrs(0x8e6a600[7], ipp://localhost/printers/ )
>>> Get-Printer-Attributes client-error-not-found: The printer or class 
>>> was not found.
>>>
>>> What does this mean?  What do I have to do to get remote printers to 
>>> show up in MacOS X application dialog boxes?
>>
>> The print dialog is asking for the attributes of printer "", which is
>> likely a bug.  It is harmless, but you can still file a bug at:
>>
>>      http://bugreport.apple.com
> 
> I see.
> 
> However, the server log produced by opening the print dialog box on the 
> Mac client also contains quite a bunch of information about the print 
> queue on the server.  It is curious that the Mac seems unwilling to use 
> that info.
> 
> Would it help if I posted the entire text of the relevant parts of the 
> server log?
> 
> -Rick
>