| Nemeth, E., Snyder, G., Hein, T. R. and Seebass, S. (2000) UNIX System Administration Handbook (3rd edn). PrenticeHall, Upper Saddle River, NJ. |
....has produced a number of study guides [Gui02] that identify important problems administrators have to solve. Mark Burgess s book [Bur00] describes the tasks performed by system administrators and generalizes the problems faced into many aphorisms. The Unix system administration handbook [NSSH01] provides indepth details about the problems faced by administrators. SAGE keeps a list [Gui] of many additional books about system administration. 2.1 A model of tasks The traditional approach for categorization is to group related papers by the problem described. Therefore, we started with ....
Evi Nemeth, Garth Snyder, Scott Seebass, and Trent R. Hein. Unix System Administration Handbook, 3rd Ed. Prentice Hall, 2001.
....functions are specified to be best effort, we support them using a snapshot of directory contents rather than with a lease. As described in subsection 2.7, the number of leases issued per file is limited for performance reasons. 3.4. 2 Namespace Consistency Shared file system namespaces commonly [34] contain regions that are private to particular users. To allow clients to modify such regions without having to frequently contact the directory group that manages the region, Farsite introduces the concept of name leases. Name leases govern which client machine currently has control over a name ....
E. Nemeth, G. Snyder, S. Seebass, T. R. Hein, UNIX System Administration Handbook, Prentice Hall, 2000.
....language. Regardless of the language, the approach is always the same for our example, we chose C. In this case, the programmer will typically write code of the form: for (i=0; i NUM; i ) pid = fork( child process calls exec( to execute remote command if (pid = 0) char av[4]; 3 av[0] rsh ; av[1] host[i] array of hostname strings av[2] bin date ; command to execute on all hosts av[3] NULL; exec( usr bin rsh , av) not reached The problem with this approach is that in addition to the parent and child processes, there are ....
E. Nemeth, G. Snyder, S. Seebass, and T. Hein. UNIX System Administration Handbook, Second Edition. Prentice-Hall, Inc. New Jersey, 1995.
....process. File descriptors data are combined with information from the system file table, with an approach similar to the one followed in the implementation of the Unix fuser utility. Aggregated information about the network usage is obtained via the invocation of the standard netstat system call [16]. 5. Distributed Monitoring and Control of SOMA Agents Any SOMA place can exploit the local MAPI component to achieve visibility of several on line monitoring indicators, to enforce a local policy for MA resource usage. In addition, since mobile agents usually act as distributed service ....
E. Nemeth, G. Snyder, T. R. Hein and S. Seebass, UNIX System Administration Handbook, Prentice Hall, Sep. 2000.
....details are available on the web site. Introduction There is relatively little prior art in print which addresses the problems of large infrastructures in any holistic sense. Thanks to the work of many dedicated people we now see extensive coverage of individual tools, techniques, and policies [nemeth] [frisch] stern] dns] evard] limoncelli] anderson] But it is difficult in practice to find a how to put it all together treatment which addresses groups of machines larger than a few dozen. Since we could find little prior art, we set out to create it. Over the course of four years of ....
Evi Nemeth, Garth Snyder, Scott Seebass, Trent R. Hein, UNIX System Administration Handbook, second edition, Prentice Hall, 1995.
....Alerts and Advise Figure 1.3. The Expert System based Process of System Performance Management 7 1.4 UNIX System Performance Management Using SPA Nemeth, Snyder, and Seebass are respected authorities in UNIX system administration. In a discussion of system performance enhancement, they say [51] For all their complexity, UNIX systems are basically plug and chug environments; as a system administrator you have almost no say in the way the kernel manages the system s resources and few ways to tune the system to your particular environment. Still, it is feasible to monitor the system to ....
....the vast majority of normal cases. As an analogy, imagine maximizing the flow of a fluid through a pipe not by exerting more pressure on the fluid (tuning the system) but by making sure the interior of the pipe is smooth, clean, and free from obstructions. Also from Nemeth, Snyder, and Seebass [51]: The best way to view a UNIX system for the purposes of analyzing performance is to think of it as a collection of disconnected, atomic resources. Usually, the only resources that need be considered in such analyses are memory, CPU, hard disks, and Ethernet. SPA considers two of these resources: ....
[Article contains additional citation context not shown here]
Nemeth, E., Snyder, G., and Seebass, S. Unix Systems Administration Handbook. Prentice-Hall, Englewood Cliffs, NJ, 1989.
....have a hierarchical topology. An example of a soft rule is that RS 232 requires communication lines to be less than 75 feet in length, but experience has shown that in normal circumstances they can safely be extended to several hundred feet. Sources of design knowledge for this domain are books [Nemeth, Snyder, Seebass 89; Tanenbaum 81; Comer 88] standards such as IEEE 802.3, product literature, and local experts. Rarely are networks designed from the ground up. There is usually too much investment in the old infrastructure and adding functionality is a process of evaluating difficult tradeoffs. It seems to be ....
E. Nemeth, G. Snyder, S. Seebass, Unix System Administration Handbook, Prentice Hall, Englewood Cliffs, NJ, 1989.
....To avoid losing data due to wear, mechanical problems, or tape deterioration, backup systems must maintain information on tape and drive usage, and must replace old tapes and schedule drive maintenance. Nemeth et al. offer additional practical advice for performing backups in UNIX environments [19]. The correctness of backup procedures must be monitored; backup software should attempt to re read tapes after dumps are complete. To guard against backup tapes that become unreadable by the tape drives that wrote them because the drive heads drift out of alignment over time, system ....
....full backup. A scheme developed at Ohio State University maintains multiple redundant backup chains , with independent sets of full and incremental backups [21] Such a scheme requires twice as many tapes and drives, but offers a high degree of reliability. 2. 9 Disaster Recovery Nemeth et al. [19] describe techniques that ensure that recovery will be possible after natural disasters. Dump tapes that contain full backups should be stored off site to prevent data loss in the event of natural disaster or fire. Backup tapes should be secured against access by unauthorized persons, since they ....
[Article contains additional citation context not shown here]
E. Nemeth, G. Snyder, S. Seebass, and T. R. Hein. UNIX System Administration Handbook. Prentice Hall, Inc., Upper Saddle River, New Jersey, 1995.
No context found.
Nemeth, E., Snyder, G., Hein, T. R. and Seebass, S. (2000) UNIX System Administration Handbook (3rd edn). PrenticeHall, Upper Saddle River, NJ.
No context found.
E. Nemeth, G. Snyder, S. Seebass, and T. Hein, "UNIX Systems Administration Handbook", Prentice Hall PTR, Englewood Cliffs, NJ, 2nd ed. 1995.
No context found.
Nemeth, Evi, et al. "UNIX System Administration Handbook." Prentice Hall: New Jersey 2001
No context found.
Nemeth, E. (ed.) (2001), Unix System Administration Handbook (3rd Edition) , Prentice-Hall. Simply the Bible of Unix system administration. This new edition covers Linux. One can actually learn operating systems and networking from this book; a must read for all computer science majors. 23
No context found.
Nemeth, E., G. Snyder, S. Seebass, and T. Hein. UNIX System Administration Handbook (2 nd edition). Upper Saddle River, NJ: Prentice-Hall PTR, 1995.
No context found.
Evi Nemeth, Garth Snyder, and Scott Seebass. UNIX System Administration Handbook. Prentice Hall, Englewood Cliffs, NJ, 1989.
No context found.
Nemeth, Evi, Garth Snyder and Scott Seebass, UNIX System Administration Handbook, Prentice Hall, Englewood Cliffs, NJ, 1989.
No context found.
[Neme95] Evi Nemeth, Garth Snyder, Scott Seebass, Trent R. Hein, Unix system administration handbook, ISBN 0-13-151051.
No context found.
Nemeth, G. Snyder, S. Seebass, Trent R. Hein, UNIX System Administration Handbook. 2 nd Edition, Prentice Hall (1995).
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC