Download LINUX Rute Users Tutorial and Exposition Version

Transcript
21.4. Package elements
21. System Services and lpd
There you can see the authors, mailing lists and points of download. If a particular
package is of much interest to you, then you should get familiar with these resources.
Good web pages will also have additional documentation like trouble-shooting guides
and FAQ’s (Frequently Asked Questions). Some may even have archives of their mailing lists. Note that some web pages are geared more toward CD vendors who are
trying to create their own distribution, and will not have packages for download that
beginner users can easily install.
User programs
These will be in one or other bin directory. In this case we can see lpq, lpr, lprm and
lptest, as well as their associated man pages.
Daemon and administrator programs
These will be in one or other sbin directory. In this case we can see lpc, lpd, lpf and
pac, as well as their associated man pages. The only daemon (background) program is
really the lpd program itself which is the core of the whole package.
Configuration files
The file /etc/printcap controls lpd. Most system services will have a file in /etc.
printcap is a plain text file that lpd reads on startup. Configuring any service primarily involves editing its configuration file. There are several graphical configuration
tools available that avoid this inconvenience (linuxconf, and printtool which is
especially for lpd) but these actually just silently produce the same configuration file.
Because printing is so integral to the system, printcap is not actually provided
by the lpr package. Trying rpm -qf /etc/printcap gives setup-2.3.4-1,
while dpkg -S /etc/printcap shows it to not be owned (i.e. part of the base system).
Service initialisation files
The files in /etc/rc.d/init.d/ (or /etc/init.d/) are the startup and shutdown
scripts to run lpd on boot and shutdown. You can start lpd yourself on the command
line with,
¨
¥
/usr/sbin/lpd
§
¦
186