• NAME
  • SYNOPSIS
  • DESCRIPTION
      is a configuration file for printers controlled by the magic filter. Every apsfilter printer in has an file of its own. There is one global apsfilterrc file that controls print characteristics for all printer. The printer-specific files have preference over the global one. Reasons for using an file are if it turns out, that you have to type in some commandline options too often or if an application is unable to parameterize the print command, so that you have to hardcode the print characteristic for such dumb applications. An enhancement to this concept are user-specific config files, that have preference over the global and the printer-specific config file. This allows configuration of print characteristics on a per-user basis. You should make use of user-specific config files instead of using the deprecated USE_USER_CODE variable, which compromises system security and is only an option on a single-user machine, see below. Select print quality (draft, lo|low, med|medium, hi|high, photo). Print uni- or bidirectional (uni, bi). Select paper type (plain, coated, glossy, premium, trans). Select color mode (color|colour, gray|grey, mono). Choose apsfilters method of data processing (auto, ascii, raw). Automatic file type recognition and automatic conversion to Postscript is apsfilters default processing method. If you want to print mostly files `as is', you can set the default to 'raw', this disables any kind of file type recognition and conversion. If you want to print mostly everything as ASCII text, then you can set this option to 'ascii'. Set the default paper size (a3, a4, legal, ledger, tabloid). Text file filter to use, when printing ASCII documents (a2ps, mpage, enscript, recode). Paper feed tray number (tray0...tray9). a2ps highlight level for pretty-printing when using a2ps or enscript as ascii filter (0, 1, 2). See also ASCII_FILTER. Whether you want headers in your text prints when using a2ps, mpage or enscript as ascii filter (header, noheader). Whether you want borders in your text prints  when using a2ps, mpage or enscript as ascii filter (border, noborder). Pages per sheet (1pps, 2pps, 4pps, 8pps). Paper orientation (landscape, portrait). Output pages in "book" format, implies commandline options "2pps,duplex,shortbind". Related options: PS_NUP, ASCII_PPS, DUPLEX, BINDING. Whether to use duplex mode or not (duplex, simplex). Paper binding edge (shortbind, longbind). Number of copies (copies=N). Enabling this option is a big potential security hole !!! If you don't understand this, DO NOT USE IT. It makes user manageable files possible which will be sourced (included/executed) during runtime of a printjob under the permissions of the calling process (lpd). This option is only valid for typical "single-user" systems, where a user wants direct access to an apsfilterrc without having to become root to make changes. A more conveniant way on a multi-user system, where security is an issue, is that a system administrator creates user-specific files. Additional informations can be found in the apsfilter handbook and in the apsfilterrc file together with some examples.
  • FILES
      apsfilter config file, settings are overwriteable by more specific printer config files, see below. apsfilter config file on a basis. This file has preference over the global config file. apsfilter config file on a basis (per print queue). This file has preference over the global and the printer queue specific config file. A config file on a per printer queue basis. This file has preference over the global, the printer queue specific and the central per user config file, which is administered by a system administrator. Enabling this has a deep impact on your systems security, especially on multi-user systems and is therefore See comments to USE_USER_CODE variable.
  • SEE ALSO
  • BUGS
      See apsfilter software center - - for new versions, bugfixes and known bugs. Please use the new tool to release bug- or problem reports. It automatically presents you a in an editor window which asks you some standard questions. If you save and quit the editor session, then this report is sent automatically via to the proper apsfilter mailinglist. If apsfilter fails to print something or prints it in a way you wouldn't expect and you want to report an apsfilter error then please save the debugging output of one print session using the new utility by typing and including the debugging output in the file into the edit session of the utility, so that it is included into the mail to the apsfilter mailinglist. Please note that you need to run /bin/sh (Bourne Shell), bash or a compatible shell, so that the above mentioned output redirection works. Under C-shell (/bin/csh) or tcsh it would't work. If you don't know, then simply make sure you use the Bournce shell by typing or then you should have no problems with redirection of and (> /dev/null 2> file.debug).
  • DOCUMENTATION
      See official apsfilter homepage Apsfilter Handbook including the Frequently Asked Questions (FAQ)
  • USER FORUM
      Please send questions to the official apsfilter help channel The above section and the file tells you how to report bugs. If you want to know how to troubleshoot your apsfilter installation, please read the manpage and as well as the carefully.
  • HISTORY
      developement started in 1994. The file on a "per printer queue" basis appeared in apsfilter 5.4.0.
Current Users: 31 © 1999-2006 Linux.com.hk PenguinSoft
All trademarks and copyrights on this page are owned by their respective companies. Linux is a trademark of Linus Torvalds.