SCIENTIFIC-LINUX-USERS Archives

September 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michael Hannon <[log in to unmask]>
Reply To:
Michael Hannon <[log in to unmask]>
Date:
Mon, 29 Sep 2008 17:49:08 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
Greetings.  We recently just updated (via a clean install) a server to
SL 5.2, x86_64.  The system had previously had a number of print queues,
but in the interest of getting home at a finite time on the day of the
upgrade, we set up only the queue for the printer that is most heavily
used.

I don't recall the details, but I certainly don't remember that there
was anything extraordinary about the process of setting up the one print
queue.

Today we attempted to revisit the issue of the print queues.  To do so,
we logged in as root at the console, typed startx, and then ran
system-config-printer (both from a terminal window and by choosing it
from the menu).

In both cases we get a pop-up message that tells us:

    Not authorized

    The password may be incorrect, or the server may be configured
    to deny remote administration.

Hmmm.  I don't know which password would be incorrect.  And I don't
understand the "remote" part.  We're logged in as "root" when this
happens, and we're logged in from the console.

To compound the mystery, we DO have the one print queue happily running.
I can't imagine how else we would have set it up.

If you have any thoughts about this, please pass 'em along.

Thanks.

					- Mike
-- 
Michael Hannon            mailto:[log in to unmask]
Dept. of Physics          530.752.4966
University of California  530.752.4717 FAX
Davis, CA 95616-8677

ATOM RSS1 RSS2