From: Tim Waugh <twaugh@redhat.com>
To: Michael Sweet <msweet@apple.com>
Cc: printing-architecture@lists.linux-foundation.org,
Eric Sandeen <sandeen@redhat.com>,
sbergman27@gmail.com
Subject: Re: [Printing-architecture] printers.conf frequently gets truncated to zero length after unclean shutdowns
Date: Tue, 23 Jul 2013 10:08:38 +0100 [thread overview]
Message-ID: <1374570518.4832.2.camel@rubik> (raw)
In-Reply-To: <0C413B5E-6225-4CF7-BF17-8E164B520D7E@apple.com>
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
On Mon, 2013-07-22 at 23:00 -0400, Michael Sweet wrote:
> The problem with fsync() is that it is a blocking API. Blocking cupsd
> (single-threaded daemon process) is *not* a good idea.
Aren't changes to printers.conf deferred anyway, to allow changes to be
batched up? So it wouldn't be an fsync call every time the values
change, but every time those values are written back -- which is much
less often on a busy system.
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2013-07-23 9:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 17:28 [Printing-architecture] printers.conf frequently gets truncated to zero length after unclean shutdowns Jiri Popelka
2013-07-22 17:46 ` Till Kamppeter
[not found] ` <51EDADB4.5000807@redhat.com>
2013-07-23 3:03 ` Michael Sweet
[not found] ` <51ED6CC4.1040501@redhat.com>
2013-07-23 3:00 ` Michael Sweet
2013-07-23 9:08 ` Tim Waugh [this message]
2013-07-23 12:08 ` Michael Sweet
[not found] ` <51EE90D7.9070607@gmail.com>
2013-07-23 16:40 ` Michael Sweet
[not found] ` <51EEBF83.2090006@gmail.com>
2013-07-23 18:16 ` Michael Sweet
[not found] ` <51EECB0D.5050208@redhat.com>
2013-07-23 18:59 ` Michael Sweet
[not found] ` <51EECDF8.9070209@gmail.com>
2013-07-23 19:01 ` Michael Sweet
2013-07-23 20:51 ` Till Kamppeter
2013-07-23 23:04 ` Michael R Sweet
2013-07-24 10:11 ` Jiri Popelka
2013-07-24 11:39 ` Michael Sweet
2013-07-26 21:36 ` Michael Sweet
[not found] ` <51F2F05E.3000207@redhat.com>
2013-07-26 22:10 ` Michael Sweet
[not found] ` <51EE1183.5080704@redhat.com>
2013-07-23 12:05 ` Michael Sweet
[not found] ` <51EEA872.4070009@redhat.com>
2013-07-23 17:51 ` Michael Sweet
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=1374570518.4832.2.camel@rubik \
--to=twaugh@redhat.com \
--cc=msweet@apple.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=sandeen@redhat.com \
--cc=sbergman27@gmail.com \
/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.