Essential System Administration: Tools and Techniques for Linux and Unix Administration, 3rd Edition
Language: English
Pages: 1178
ISBN: 0596003439
Format: PDF / Kindle (mobi) / ePub
Essential System Administration,3rd Edition is the definitive guide for Unix system administration, covering all the fundamental and essential tasks required to run such divergent Unix systems as AIX, FreeBSD, HP-UX, Linux, Solaris, Tru64 and more. Essential System Administration provides a clear, concise, practical guide to the real-world issues that anyone responsible for a Unix system faces daily.The new edition of this indispensable reference has been fully updated for all the latest operating systems. Even more importantly, it has been extensively revised and expanded to consider the current system administrative topics that administrators need most. Essential System Administration,3rd Edition covers: DHCP, USB devices, the latest automation tools, SNMP and network management, LDAP, PAM, and recent security tools and techniques.Essential System Administration is comprehensive. But what has made this book the guide system administrators turn to over and over again is not just the sheer volume of valuable information it provides, but the clear, useful way the information is presented. It discusses the underlying higher-level concepts, but it also provides the details of the procedures needed to carry them out. It is not organized around the features of the Unix operating system, but around the various facets of a system administrator's job. It describes all the usual administrative tools that Unix provides, but it also shows how to use them intelligently and efficiently.Whether you use a standalone Unix system, routinely provide administrative support for a larger shared system, or just want an understanding of basic administrative functions, Essential System Administration is for you. This comprehensive and invaluable book combines the author's years of practical experience with technical expertise to help you manage Unix systems as productively and painlessly as possible.
only_from = 192.168.10.0 localhost no_access = dalton.ahania.com access_times = 07:00-20:00 banner_fail = /usr/etc/deny_banner } The only_from entry specifies the hosts that are allowed to use this service; requests from any remote host not on the specified subnet will be refused. The no_access entry performs the opposite function and denies access to the specified host(s). The access_times entry specifies when the service is available to users who are allowed to use it. The final entry
satellite sources. You can obtain the authoritative time values for your network from external stratum 1 NTP servers on the Internet. This is in fact the most common practice for Internet-connected organizations that do not require the extreme precision needed for a few real-time applications (e.g., air traffic control). The web page http://www.eecis.udel.edu/~mills/ntp/servers.htm contains links to lists of Internet-accessible stratum 1 and 2 servers. For most sites, a stratum 2 server is
answering. The final line lists the recipient address. Several different types of files may be present in the work queue directory; all have names consisting of a prefix plus the message ID. The prefix indicates the file content type: qf Control file (includes message headers) df Data file (message text) xf Holds mailer error messages ("transcript file") Qf Indicates a bounced message tf Temporary file used as scratch when the qf file is being updated Tf Message processing
/etc/vfstab files. Tip Tru64 also has a vold daemon. However, it is part of its Logical Storage Manager facility and thus performs a completely different function. * * * [13] Also, the disk tracks are concentric, not continuous, as they are on an LP. If you don't know what an LP is, think of it as a really wide CD (about 12" diameter) with data on both sides. [14] I'm using this term in a descriptive sense only. Technically, a disk cylinder consists of the same set of tracks on
cpio -ov > /dev/rmt0) >& $toc The file lists produced by cpio commands like these contain only the pathnames of the files in the archive. If you want a more detailed listing, you can generate it with a second cpio command or a more complex pipe leading up to the cpio backup command: $ cpio -itv < /dev/rmt0 > $toc $ find /home | cpio -o | tee /dev/rmt0 | cpio -t -i -v > $toc The first command lists the files in the archive on tape. The second command avoids having to reread the backup tape by