Mailinglist Archive: opensuse (3605 mails)

< Previous Next >
Re: [SLE] lppasswd policy
  • From: "PerfectReign" <kai@xxxxxxxxxxxxxxxx>
  • Date: Fri, 23 Jun 2006 09:45:36 -0500
  • Message-id: <E1Ftmue-0002gz-O0@xxxxxxxxxxxxxxx>


> On 22/06/06 22:24, kai wrote:
> >On Thursday 22 June 2006 05:52 pm, Darryl Gregorash wrote:
> >
> >>On 22/06/06 18:38, Carlos E. R. wrote:
> >>
> >>>The Thursday 2006-06-22 at 16:36 +0200, Hans du Plooy wrote:
> >>>
> >>>><sigh> Thanks. Was hoping to avoid having another password to
> >>>>remember...
> >>>>
> >>>Change root's password to something else. Then, set cup's to the
previous
> >>>root's password. Then, reset Mr. root password.
> >>>
> >>>;-)
> >>>
> >>You've missed the point. A password for CUPS "must be at least 6
> >>characters long, cannot contain your username, and must contain at least
> >>one letter and number."
> >>
> >>The system and CUPS passwords are stored in different places, so it is
> >>possible for them to be the same -- so long as the above conditions
apply.
> >>
> >
> >
> >Interesting solution. I hadn't heard of doing this.
> >
> >I still find it odd that CUPS needs a non-root password...
> >
> >I'll try it out for a few systems (which have the passwords written
on sticky
> >notes) and let you know how it goes.
> >
> >
> Note what Johannes wrote; CUPS doesn't need any passwords at all, if you
> are only going to use Yast for printer administration. The password is
> only needed if you intend to use the CUPS web interface
> (http://localhost:631)
>

Pardon my ignorance - since I'm just a newbie - but IIRC, you can't do
queue management from within YaST. I just looked at the online help and
didn't see anything about YaST doing queue management for print jobs.
(For example, releasing or restarting a stalled print job.)

Is there something I'm missing?

--
kai ponte
www.perfectreign.com || www.filesite.org

The internet: http://welcome.twysted.net/


--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx


< Previous Next >
Follow Ups