The default program is "none".
The specified port monitor must be listed in the printer's PPD file.
<dt><b>-o printer-error-policy=</b><i>name</i>
-<dd style="margin-left: 5.0em">Sets the error policy to be used when the printer backend is unable to send the job to the printer.
-The name must be one of "abort-job", "retry-job", "retry-current-job", or "stop-printer".
+<dd style="margin-left: 5.0em">Sets the policy for errors such as printers that cannot be found or accessed, don't support the format being printed, fail during submission of the print data, or cause one or more filters to crash.
+The name must be one of "abort-job" (abort the job on error), "retry-job" (retry the job at a future time), "retry-current-job" (retry the current job immediately), or "stop-printer" (stop the printer on error).
The default error policy is "stop-printer" for printers and "retry-current-job" for
classes.
<dt><b>-o printer-is-shared=true</b>
<h2 class="title"><a name="CONFORMING_TO">Conforming To</a></h2>
Unlike the System V printing system, CUPS allows printer names to contain any printable character except SPACE, TAB, "/", or "#".
Also, printer and class names are <i>not</i> case-sensitive.
-Finally, the CUPS version of <b>lpadmin</b> may ask the user for an access password depending on the printing system configuration.
+<p>Finally, the CUPS version of <b>lpadmin</b> may ask the user for an access password depending on the printing system configuration.
This differs from the System V version which requires the root user to execute this command.
<h2 class="title"><a name="NOTES">Notes</a></h2>
The CUPS version of <b>lpadmin</b> does not support all of the System V or Solaris printing system configuration options.
-Interface scripts are not supported for security reasons.
+<p>Interface scripts are not supported for security reasons.
<p>The double meaning of the <b>-E</b> option is an unfortunate historical oddity.
+<p>The <b>lpadmin</b> command communicates with the scheduler (<b>cupsd</b>) to make changes to the printing system configuration.
+This configuration information is stored in several files including <i>printers.conf</i> and <i>classes.conf</i>.
+These files should not be edited directly and are an implementation detail of CUPS that is subject to change at any time.
<h2 class="title"><a name="EXAMPLE">Example</a></h2>
Create an IPP Everywhere print queue:
<pre class="man">