All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: Michael Sweet <msweet@apple.com>
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] CUPS systemd issues
Date: Thu, 16 Oct 2014 09:09:21 +0100	[thread overview]
Message-ID: <1413446961.20196.0.camel@redhat.com> (raw)
In-Reply-To: <02668022-214A-4993-B2BE-C3C25730BAFD@apple.com>

[-- Attachment #1: Type: text/plain, Size: 394 bytes --]

On Wed, 2014-10-15 at 15:27 -0400, Michael Sweet wrote:
> 1. Remove the localhost listeners from the org.cups.cupsd.socket file
> and just run-on-demand based on local domain socket IO. When the web
> interface is enabled we can disable the on-demand mode, just as we do
> when printer sharing is enabled or when there are pending jobs.

I think this is the best approach.

Tim.
*/


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 465 bytes --]

      parent reply	other threads:[~2014-10-16  8:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 19:27 [Printing-architecture] CUPS systemd issues Michael Sweet
2014-10-16  0:22 ` Ira McDonald
2014-10-16  8:09 ` Tim Waugh [this message]

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=1413446961.20196.0.camel@redhat.com \
    --to=twaugh@redhat.com \
    --cc=msweet@apple.com \
    --cc=printing-architecture@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.