Interface scripts are no longer supported for security reasons

[thirdparty/cups.git] / doc / help / man-filter.html

diff --git a/doc/help/man-filter.html b/doc/help/man-filter.html
index bb4f620bcb9e41257fd7c03c344509a399e70b1b..33a35563e8e38a2d951ac46689462326e4c02ed4 100644 (file)
--- a/doc/help/man-filter.html
+++ b/doc/help/man-filter.html
@@ -163,10 +163,7 @@ for a regular print file.
 <dd style="margin-left: 5.0em">The user executing the filter, typically "lp" or "root"; consult the <i>cups-files.conf</i> file for the current setting.
 </dl>
 <h2 class="title"><a name="CONFORMING_TO">Conforming To</a></h2>
-While the filter interface is compatible with System V interface
-scripts, it will only work with the System V interface script as the
-only filter.  Typically the interface script will be provided via the
-<i>lpadmin(8)</i> command using the <i>-i</i> option.
+While the filter interface is compatible with System V interface scripts, CUPS does not support System V interface scripts.
 <h2 class="title"><a name="NOTES">Notes</a></h2>
 CUPS filters are not meant to be run directly by the user.
 Aside from the legacy System V interface issues (<i>argv[0]</i> is the printer name), CUPS filters also expect specific environment variables and file descriptors, and typically run in a user session that (on OS X) has additional restrictions that affect how it runs.