From: Tim Waugh <twaugh@redhat.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CUPS plugin discovery bits
Date: Wed, 23 May 2007 16:57:07 +0100 [thread overview]
Message-ID: <1179935827.4854.17.camel@cyberelk.elk> (raw)
In-Reply-To: <1179935471.19944.6.camel@aeonflux.holtmann.net>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
On Wed, 2007-05-23 at 17:51 +0200, Marcel Holtmann wrote:
> The thing that worries me is when you start CUPS it will list through
> all backends and make them list. So on every boot the system will scan
> for devices in range and that can slow down the system boot. So this
> might not be a good idea. Actually that is the reason why we wanna go
> for a printing service in the future.
This hasn't been true since CUPS 1.1.x. In CUPS 1.2.x device discovery
is performed on demand.
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-23 15:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 15:24 [Bluez-devel] CUPS plugin discovery bits Bastien Nocera
2007-05-23 15:51 ` Marcel Holtmann
2007-05-23 15:57 ` Tim Waugh [this message]
2007-05-23 16:15 ` Bastien Nocera
2007-05-23 16:26 ` Bastien Nocera
2007-05-23 16:56 ` Johan Hedberg
2007-05-23 17:07 ` Bastien Nocera
2007-05-24 13:39 ` Bastien Nocera
2007-05-24 15:31 ` Johan Hedberg
2007-05-24 18:49 ` Bastien Nocera
2007-05-25 12:30 ` Bastien Nocera
2007-05-25 12:58 ` Bastien Nocera
2007-05-25 15:08 ` Bastien Nocera
2007-05-29 3:58 ` Luiz Augusto von Dentz
2007-05-29 10:26 ` Bastien Nocera
2007-05-29 13:18 ` Luiz Augusto von Dentz
2007-05-29 13:37 ` Marcel Holtmann
2007-06-07 10:21 ` Marcel Holtmann
2007-06-07 12:59 ` Bastien Nocera
2007-05-24 15:03 ` Bastien Nocera
2007-05-24 15:20 ` Marcel Holtmann
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=1179935827.4854.17.camel@cyberelk.elk \
--to=twaugh@redhat.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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