diff options
Diffstat (limited to 'doc/help')
| -rw-r--r-- | doc/help/man-cups-files.conf.html | 8 | ||||
| -rw-r--r-- | doc/help/man-cupsaddsmb.html | 2 | ||||
| -rw-r--r-- | doc/help/policies.html | 4 | ||||
| -rw-r--r-- | doc/help/ref-cups-files-conf.html.in | 25 |
4 files changed, 35 insertions, 4 deletions
diff --git a/doc/help/man-cups-files.conf.html b/doc/help/man-cups-files.conf.html index 8c3a610f..3e30a9d9 100644 --- a/doc/help/man-cups-files.conf.html +++ b/doc/help/man-cups-files.conf.html @@ -140,6 +140,14 @@ be found. <dd></dd> <dd>Specifies the directory where the server configuration files can be found. </dd> +<dt>SyncOnClose Yes +</dt> +<dd></dd> +<dt>SyncOnClose No +</dt> +<dd>Specifies whether the scheduler calls <i>fsync(2)</i> after writing configuration +or state files. The default is No. +</dd> <dt>SystemGroup group-name [group-name ...] </dt> <dd></dd> diff --git a/doc/help/man-cupsaddsmb.html b/doc/help/man-cupsaddsmb.html index 0bb0ddcd..cc4e46e6 100644 --- a/doc/help/man-cupsaddsmb.html +++ b/doc/help/man-cupsaddsmb.html @@ -162,8 +162,6 @@ Getting the full set of Windows driver files should be easier. <h2 class="title"><a name="SEE_ALSO">See Also</a></h2> <i>smbd(8)</i>, <i>smb.conf(5)</i>, <a href='http://localhost:631/help'>http://localhost:631/help</a> -<br> -<a href='http://www.cups.org/windows/'>http://www.cups.org/windows/</a> <h2 class="title"><a name="COPYRIGHT">Copyright</a></h2> Copyright 2007-2013 by Apple Inc. diff --git a/doc/help/policies.html b/doc/help/policies.html index 18f4c80e..42b789aa 100644 --- a/doc/help/policies.html +++ b/doc/help/policies.html @@ -39,7 +39,7 @@ HREF="ref-cupsd-conf.html#LimitIPP"><TT>Limit</TT></A> subsections which list th 7 8 # All administration operations require an administrator to authenticate... - 9 <Limit CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class + 9 <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default> 10 AuthType Default 11 Require user @SYSTEM @@ -100,7 +100,7 @@ HREF="ref-cupsd-conf.html#LimitIPP"><TT>Limit</TT></A> subsections which list th <P>The access control rules are listed after the <TT>Limit</TT> line and are the same as those used for <A HREF="ref-cupsd-conf.html#Location"><TT>Location</TT></A> sections. In this case, we require the owner of the job ("@OWNER") or a member of the <A HREF="ref-cupsd-conf.html#SystemGroup"><TT>SystemGroup</TT></A> ("@SYSTEM") to do the operation. Because we do not include an <A HREF="ref-cupsd-conf.html#AuthType"><TT>AuthType</TT></A> directive here, the user information can come from the IPP request itself or the authenticated username from the HTTP request. The administrative operations starting on line 9, however, <em>do</em> use the <TT>AuthType</TT> directive, and so administrative operations need to be authenticated:</P> <PRE CLASS="example"> - 9 <Limit CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class + 9 <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default> 10 AuthType Default 11 Require user @SYSTEM diff --git a/doc/help/ref-cups-files-conf.html.in b/doc/help/ref-cups-files-conf.html.in index 171950c5..70c996f4 100644 --- a/doc/help/ref-cups-files-conf.html.in +++ b/doc/help/ref-cups-files-conf.html.in @@ -429,6 +429,31 @@ to resolve relative paths in the <VAR>cupsd.conf</VAR> file. The default server directory is <VAR>/etc/cups</VAR>.</P> +<H2 CLASS="title"><SPAN CLASS="info">CUPS 1.6.4</SPAN><A NAME="SyncOnClose">SyncOnClose</A></H2> + +<H3>Examples</H3> + +<PRE CLASS="command"> +SyncOnClose No +SyncOnClose Yes +</PRE> + +<H3>Description</H3> + +<P>The <CODE>SyncOnClose</CODE> directive determines whether the scheduler +flushes changes to configuration and state files to disk. The default is +<CODE>No</CODE> which relies on the operating system to schedule a suitable +time to write changes to disk.</P> + +<BLOCKQUOTE><B>Note:</B> + +<P>Setting <CODE>SyncOnClose</CODE> to <CODE>Yes</CODE> makes the scheduler use the <CODE>fsync(2)</CODE> system call to write all changes to disk, however the drive or network file system server may still delay writing data to disk. Do not depend on this functionality to prevent data loss in the event of unexpected hardware failure.</P> + +<P>Enabling <CODE>SyncOnClose</CODE> may also cause the scheduler to periodically become unresponsive while it waits for changes to be written.</P> + +</BLOCKQUOTE> + + <H2 CLASS="title"><A NAME="SystemGroup">SystemGroup</A></H2> <H3>Examples</H3> |