The Experts below are selected from a list of 18057 Experts worldwide ranked by ideXlab platform
Lincoln Stein - One of the best experts on this subject based on the ideXlab platform.
-
Current Protocols in Bioinformatics - X Window System Survival Guide
Current protocols in human genetics, 2007Co-Authors: Lincoln SteinAbstract:Logging in to a Unix System from a console typically initiates a graphical desktop environment that is similar to the Microsoft Windows and Apple Macintosh desktops. Logging in remotely to a Unix System, however, typically limits the user to a small text-only window, which is unable to launch graphical applications. This appendix describes the two main options for overcoming this obstacle: a Virtual Network Computer (VNC) and the X Window System.
-
Current Protocols in Bioinformatics - X Window Survival Guide
Current protocols in human genetics, 2002Co-Authors: Lincoln SteinAbstract:Logging-in to a Unix System from a console typically initiates a graphical desktop environment that is similar to the Microsoft Windows and Apple Macintosh desktops. Logging-in remotely to a Unix System, however, typically limits the user to a small text-only window, which is unable to launch graphical applications. This appendix describes the two main options for overcoming this obstacle: a Virtual Network Computer (VNC) and the X Window System.
Lincoln D Stein - One of the best experts on this subject based on the ideXlab platform.
-
X Window System survival guide.
Current protocols in bioinformatics, 2007Co-Authors: Lincoln D SteinAbstract:Logging in to a Unix System from a console typically initiates a graphical desktop environment that is similar to the Microsoft Windows and Apple Macintosh desktops. Logging in remotely to a Unix System, however, typically limits the user to a small text-only window, which is unable to launch graphical applications. This appendix describes the two main options for overcoming this obstacle: a Virtual Network Computer (VNC) and the X Window System.
Rémy Evard - One of the best experts on this subject based on the ideXlab platform.
-
LISA - An Analysis of Unix System Configuration
1997Co-Authors: Rémy EvardAbstract:Management of operating System configuration files files is an essential part of Unix Systems administration. It is particularly difficult in environments with a large number of computers. This paper presents a study of Unix configuration file management. It compares existing Systems and tools from the literature, presents several case studies of configuration file management in practice, examines one site in depth, and makes numerous observations on the configuration process.
-
an analysis of Unix System configuration
USENIX Large Installation Systems Administration Conference, 1997Co-Authors: Rémy EvardAbstract:Management of operating System configuration files files is an essential part of Unix Systems administration. It is particularly difficult in environments with a large number of computers. This paper presents a study of Unix configuration file management. It compares existing Systems and tools from the literature, presents several case studies of configuration file management in practice, examines one site in depth, and makes numerous observations on the configuration process.
Carl Erickson - One of the best experts on this subject based on the ideXlab platform.
-
extending Unix System logging with sharp
USENIX Large Installation Systems Administration Conference, 2000Co-Authors: Matthew Bing, Carl EricksonAbstract:System messages in a Unix System are handled by syslog. The responsibilities of syslog are to filter and disperse program generated messages based on a priority code contained in each message. Filtering with priority codes is not sufficient to generate enough usable information for the System administrator. Utilities which do regular expression parsing of syslog messages typically do not run continuously and thus are limited by a lack of state in detecting potentially important patterns in syslog messages.SHARP (Syslog Heuristic Analysis and Response Program) improves the monitoring of Systems by extending the existing syslog infrastructure with programmable modules. These modules use a library with a simple API to perform near real time analysis based on the messages they register to receive. System administrators can use SHARP to improve the services provided by their Systems without the need for constant manual evaluation of message logs. The SHARP System and several modules were tested in a higher education production environment during the spring of 2000. Experience with SHARP indicates that it is stable, reliable, and improves the overall operation of a laboratory while not significantly increasing the workload on the System administrator.
-
LISA - Extending Unix System Logging with SHARP
2000Co-Authors: Matthew Bing, Carl EricksonAbstract:System messages in a Unix System are handled by syslog. The responsibilities of syslog are to filter and disperse program generated messages based on a priority code contained in each message. Filtering with priority codes is not sufficient to generate enough usable information for the System administrator. Utilities which do regular expression parsing of syslog messages typically do not run continuously and thus are limited by a lack of state in detecting potentially important patterns in syslog messages.SHARP (Syslog Heuristic Analysis and Response Program) improves the monitoring of Systems by extending the existing syslog infrastructure with programmable modules. These modules use a library with a simple API to perform near real time analysis based on the messages they register to receive. System administrators can use SHARP to improve the services provided by their Systems without the need for constant manual evaluation of message logs. The SHARP System and several modules were tested in a higher education production environment during the spring of 2000. Experience with SHARP indicates that it is stable, reliable, and improves the overall operation of a laboratory while not significantly increasing the workload on the System administrator.
Stephen Rago - One of the best experts on this subject based on the ideXlab platform.
-
Unix System v network programming
1993Co-Authors: Stephen RagoAbstract:(Each chapter ends with a Summary, Exercises, Bibliographic Notes.) Preface. I. BACKGROUND MATERIAL. 1. Introduction to Networks. Background. Network Characteristics. Networking Models. 2. Unix Programming. Overview. Concepts. Conventions. Writing Programs. Summary. Exercise. II. USER-LEVEL NETWORK PROGRAMMING. 3. STREAMS. STREAMS Background. STREAMS Architecture. System Calls. Nonblocking I/O and Polling. Service Interfaces. IPC with STREAMS Pipes. Advanced Topics. 4. The Transport Layer Interface. Introduction. Transport Endpoint Management. Connectionless Service. Connection-oriented Service. TLI and Read/Write. 5. Selecting Networks and Addresses. Introduction. Network Selection. Name-to-Address Translation. Name-to-Address Library. Design. 6. The Network Listener Facility. The Service Access Facility. Port Monitors. The Listener Process. One-shot Servers. Standing Servers. The NLPS Server. 7. Sockets. Introduction. Socket Management. Connection Establishment. Data Transfer. Unix Domain Sockets. Advanced Topics. Comparison with the TLI. Name-to-Address Translation. 8. Remote Procedure Calls. Introduction. XDR. High-level RPC Programming. Low-level RPC Programming. rpcgen. Advanced RPC Features. III. KERNEL-LEVEL NETWORK PROGRAMMING. 9. The STREAMS SubSystem. The Kernel Environment. The STREAMS Environment. STREAMS Messages. STREAMS Queues. Communicating with Messages. Message Types. 10. STREAMS Drivers. Introduction. Driver Entry Points. The Data Link Provider Interface. Ethernet Driver Example. 11. STREAMS Modules. Introduction. Module Entry Points. The Terminal Interface. Network TTY Emulator Example. 12. STREAMS Multiplexors. Introduction. How Multiplexors Work. The Transport Provider Interface. Transport Provider Example. IV. DESIGN PROJECT: IMPLEMENTING SLIP. 13. Design Project: Implementing SLIP. Introduction to SLIP. Software Architecture. User-level Components. Kernel-level Components. Bibliography. Index. 0201563185T04062001
-
Unix System v network programming
1993Co-Authors: Stephen RagoAbstract:(Each chapter ends with a Summary, Exercises, Bibliographic Notes.) Preface. I. BACKGROUND MATERIAL. 1. Introduction to Networks. Background. Network Characteristics. Networking Models. 2. Unix Programming. Overview. Concepts. Conventions. Writing Programs. Summary. Exercise. II. USER-LEVEL NETWORK PROGRAMMING. 3. STREAMS. STREAMS Background. STREAMS Architecture. System Calls. Nonblocking I/O and Polling. Service Interfaces. IPC with STREAMS Pipes. Advanced Topics. 4. The Transport Layer Interface. Introduction. Transport Endpoint Management. Connectionless Service. Connection-oriented Service. TLI and Read/Write. 5. Selecting Networks and Addresses. Introduction. Network Selection. Name-to-Address Translation. Name-to-Address Library. Design. 6. The Network Listener Facility. The Service Access Facility. Port Monitors. The Listener Process. One-shot Servers. Standing Servers. The NLPS Server. 7. Sockets. Introduction. Socket Management. Connection Establishment. Data Transfer. Unix Domain Sockets. Advanced Topics. Comparison with the TLI. Name-to-Address Translation. 8. Remote Procedure Calls. Introduction. XDR. High-level RPC Programming. Low-level RPC Programming. rpcgen. Advanced RPC Features. III. KERNEL-LEVEL NETWORK PROGRAMMING. 9. The STREAMS SubSystem. The Kernel Environment. The STREAMS Environment. STREAMS Messages. STREAMS Queues. Communicating with Messages. Message Types. 10. STREAMS Drivers. Introduction. Driver Entry Points. The Data Link Provider Interface. Ethernet Driver Example. 11. STREAMS Modules. Introduction. Module Entry Points. The Terminal Interface. Network TTY Emulator Example. 12. STREAMS Multiplexors. Introduction. How Multiplexors Work. The Transport Provider Interface. Transport Provider Example. IV. DESIGN PROJECT: IMPLEMENTING SLIP. 13. Design Project: Implementing SLIP. Introduction to SLIP. Software Architecture. User-level Components. Kernel-level Components. Bibliography. Index. 0201563185T04062001
