public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Vermeulen <swift@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: printing-howto.xml
Date: Sat, 03 May 2008 15:59:39 +0000	[thread overview]
Message-ID: <E1JsK9D-0006M4-2x@stork.gentoo.org> (raw)

swift       08/05/03 15:59:39

  Modified:             printing-howto.xml
  Log:
  Mentioned in #188993 - HTTPS to CUPS takes a while due to SSL certificate generation

Revision  Changes    Path
1.69                 xml/htdocs/doc/en/printing-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/printing-howto.xml?rev=1.69&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/printing-howto.xml?rev=1.69&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/printing-howto.xml?r1=1.68&r2=1.69

Index: printing-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -r1.68 -r1.69
--- printing-howto.xml	20 Feb 2008 21:07:27 -0000	1.68
+++ printing-howto.xml	3 May 2008 15:59:38 -0000	1.69
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.68 2008/02/20 21:07:27 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.69 2008/05/03 15:59:38 swift Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -24,8 +24,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>2.99</version>
-<date>2008-02-20</date>
+<version>2.100</version>
+<date>2008-05-03</date>
 
 <chapter>
 <title>Printing and Gentoo Linux</title>
@@ -586,6 +586,13 @@
 administrative tasks.
 </p>
 
+<note>
+If you use an HTTPS connection to CUPS, the first time you access the interface
+it will take a very long time before the site comes up. This is because the
+first request triggers the generation of the CUPS SSL certificates which is a
+very time-consuming job (up to several dozens of minutes).
+</note>
+
 <p>
 Go to <e>Administration</e> and enter your root login and password information
 at the box. Then, when you have reached the administrative interface, click on



-- 
gentoo-doc-cvs@lists.gentoo.org mailing list



             reply	other threads:[~2008-05-03 15:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-03 15:59 Sven Vermeulen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-16  1:08 [gentoo-doc-cvs] cvs commit: printing-howto.xml Joshua Saddler
2008-05-07  0:29 Joshua Saddler
2008-05-03 16:00 Sven Vermeulen
2008-02-20 21:07 Sven Vermeulen
2007-02-05 14:14 Xavier Neys
2007-02-02  8:10 Josh Saddler
2006-11-28 19:21 Josh Saddler
2006-11-28 18:10 Josh Saddler
2006-09-14 11:21 Josh Saddler
2006-09-04  2:19 Josh Saddler
2006-09-04  1:50 Josh Saddler
2006-03-20 20:21 Josh Saddler
2006-03-19 17:29 Josh Saddler
2006-03-14 18:55 Josh Saddler
2006-03-11 16:21 swift
2006-03-05 10:29 swift
2005-11-21 15:44 Xavier Neys
2005-11-05 17:29 swift
2005-09-09 13:19 Jan Kundrat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1JsK9D-0006M4-2x@stork.gentoo.org \
    --to=swift@stork.gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox