[Printing-architecture] printers.conf frequently gets truncated to zero length after unclean shutdowns

Tim Waugh twaugh at redhat.com
Tue Jul 23 09:08:38 UTC 2013

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.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 482 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxfoundation.org/pipermail/printing-architecture/attachments/20130723/d9823018/attachment-0001.sig>

More information about the Printing-architecture mailing list