For the Abstract.The-Revision Deletion, Orcreation,Of Sentences Is

Total Page:16

File Type:pdf, Size:1020Kb

For the Abstract.The-Revision Deletion, Orcreation,Of Sentences Is DOCUMENT REBUKE ED 071 886 LI.004 082 AUTHOR Mathis, Betty. Ann TITLE Techniques for the Evaluation and IMprovement of Computer-Produced Abstracts. INSTITUTION Ohio State Univ".Colulbus..Computer and Information Science, Research.Center.. SPONS AGENCY National Science Foundation, Washington, D.C. REPORT NO OSU-CISRC-TR-15 . PUB DATE Dec 72 NOTE 275p.;(202 References) EDRS PRICE MF-30.65 HC-49.87 DESCRIPTORS *Abstracting;,,Abstracts; Algorithms; *Automation; CoMputers; *Electrohit Data Processing; Evaluation; Periodicals IDENTIFIERS *Automatic Abstracting ABSTRACT An automatic abstracting system, named ADAM, implemented on the IBM 370, receives journal.articles as input and produces abstracts as output. An algorithm has- been.developed which considers every sentence in the input text and rejects sentences which, are not suitable for inclusion in the abstract. All sentences which are not rejected are included in the set of sentences which are candidates for inclusion in the abstract.,The quality of the abstracts can be evaluated by means of a two -step evaluation procedUre.,The 'first step determines the conforMity of the abstracts to the defined criteria for an acceptable abstract The aecond step provides an objective evaluation criterion for abstract quality based on a.compsrison of the abstract with 'its parent documere,-. Based on the results of this evaluation, several techniques have been developed to improve the quality of the abstracts. These procedures -modify the form, arrangement, and content of the sentences selected for the abstract.The-revision deletion, orcreation,of sentences is perfOrmed according to a number of generalized ruletwhich are based on the structural characteriitics of the sentences.. This modification produces' abstracts in which the flow of ideas is improved and which represent a more nearly cohcrent:whole..(AuthorISJ) - - TECIfigICAL REPORT SERIES 4 CO1PUTE13 1r1fiFilliTTO S. -SCIENCE FiESEFIliCii CENTER. , THE OHIO STATE UNIVERSITY COLUMBUS, OHIO U.S. DEPARTMENT OF HEALTH, (OSU:-CISRC-TR-72 -15) EDUCATION & WELFARE OFFICE OF EDUCATION THIS DOCUMENT HAS BEEN REPRO. OUCEO EXACTLY AS RECEIVED FROM THE PERSON OR ORGANIZATION ORIG. MATING IT, POINTS OF VIEW OR OPIN. IONS STATED DO NOT NECESSARILY REPRESENT OFFICIAL OFFICE OF EOU CATION POSITION OR POLICY. TECHNIQUES FOR THE EVALUATION AND IMPROVEMENT OF COMPUTER-PRODUCED ABSTRACTS by Betty Ann Mathis Work performed under Grant No. 534.1, National Science Foundation Computer and Information Science Research Center The Ohio State University Columbus,'Ohio 43210 ,December 1972 ABSTRACT An,authomatic abstracting system, named ADAM, has been implemented on the IBM 370. ADAM receives journal articles as input and produces abstracts as output. An-algorithm.has been developed which considers every sentence in the input text,and rejects sentences which are not suitable for inclusion in the abstract. All sentences which are not rejected are included in the set of sentences which are candidates for inclusion:in the abstract. The quality of the abstracts can be evaluated by means ofa two-step evaluation procedure. The first step,of the procedure determines the con- formity of the abstracts. to the defined- criteria for an acceptable abstract aSti for the given system. The second step provides an objective evaluation criterion for abstract quality based on a _comparison of the abstract with its parent document. The second step is based on the assumption that an abstract should present the maximum amount of data from the parent document in the minimum amount of length. Based on the results of this evaluation, several techniques hive been developed to improve the quality of the abstracts. These procedures modify the form, arrangement, and-content of the sentences selected for theab- stract. The revision,, deletion, or creation of sentences is performed according to a number of generalized rules whichare based on the structunAl chatacteristics of the sentences-. This modification produces abstracts in which the flow of ideas is improved and whichrepresent a more nearly coher- ent whole. The abstracts also show improvement accordingto the objective evaluation criteria: ii PREFACE This work was done in partial fulfillment of the requirements for a doctor of philosophy degree in Computer and Information Science from The Ohio State University. It was supported in part by Grant No. GN 534.1 from the Office of Science Information Seryice, National Science Founda tion, to the Computer and Information Science Research Center of The Ohio State.University The CoMPuter and Information Science Research Center of The Ohio State University is an interdisciplinary research organization which consists of the staff, graduate students, and faculty of many University departments and laboratories. This report is based on research accom plished in cooperation with the Department of Computer-and Information Science. The research was administered and monitored by The Ohio State University Research Foundation. 1 vso ACKNOWLEDGEMENTS I am indebted'to my adviser, Dr. James E. Rush, for his help and advice during the preparation qt this dissertition and throughout my graduate career. I am also grateful to the other two members of my reading committee, Dr. Marshal C. Yovitg. and Dr. Anthony E. Petrarca for their contributions to this work. My graduate studies have been enriched by courses taught by Professors Ernst, Foulk",*Lazorick, Liu, Montgomery, Petrarca, Rustagi, Reeker, Rush, Seltzer, White and Yovits. Richard Salvador and Antonio Zamora worked with Dr. Rush on the original design of ADAM and I wish to thank them for allowingme to continue work,on their system. I also'wish to thank Carol E. Young for allowing me to use her grammatical class assignment programs in my 'research. I am grateful to Dr. Bertrand C. Landry for reading one of the early drafts of this dissertation and for providing valuable Suggestions. Michael McCabe helped me with some of the programming of ADAM and Iam appreciative of his assistance. I also wish to thank the students in the undergraduate information storage and retrieval courses-who tested the abstracting system. Thanks is also due to my typiSts, Mrs. .Mary Kimball and Mrs. Constance Fitzpatrick. pilling my graduate-studies, I received financial aid froMa. University Fellowship and research support froM a grant (GN-534.1) from the National Science Foundation to the Computer and information Science Research Center. Computer time for this research was provided by the grant and The Ohio State University Instruction and Research Computer Center. A special wOrd of thanks' is due my parents, my brother and Mike for their help and encouragement. iv ,f TABLE OF CONTENTS ABSTRACT PREFACE ACKNOWLEDGEMENTS iv LIST OF TABLES i ix LIST OF FIGURES QUOTATION REFERENCE xiv Chapter I. Introduction 1 1. TheNeed for Abstracting 1 2, The Need for Abstracts in the Scientific Community. 2 3, The Production of Abstracts by Computer 3 4. The Scope of the Dissertation 4 Reference§ 6 II. Background and RevieW of Previous Work 7 1. The Nature and Definition of Abstraction 7 1.1. Introduction 7 1.2. Historical Development of Abstracting 8 1.3. Intensional Properties of Abstracts 12 1.4. Formal Definition of an "Abstract" 19 2. Methods of Producing Abstracts 22 2.1. Human Abstracting Systems 22 2.1:1. .0perational Systems 24 2.1.2: Selection and Consistency 29 2.2. Computerbased Abstracting Systems 39 2.2.1. Basic System Components 40 2.2.2. Major Research tffarts-in the Rroduction of Abstracts 42 2.2.2.1. The Luhn Study 42 2.2.2.2.The ACSIMatic Study . 44 v e, 2.2.2.3. The Oswald Study i.2.2.4.1 Word Association Research 50 , . 2.2.2.5.- The TRW Study ..... 53 2.2.2.6. The Earl Study 58 2.2.2.7, The Soviet Study 64 References 69 III. Des,ign of the Abstracting System 7'5 1. Philosophy Underlying the Design 75 2. Data Input 77 3. Methods of Sentence Selection and Rejection 78 3.1. Sentence Elimination 78 3.2. Location criteria 79 3.3. "Cue" Criteria 80 3.4. Intersentence Reference 82 3.5. Frequency Criteria 83 3.6. Coherence Considerations 84 4, The Word Control List 84 4.1. Hierarchical Rules for Implementing the Functions in the Word Control List 85 4.2. Syntactic Valuesand Their Use 85 5. Summary of the 'Operation of the Abstracting System , 87 References 91 IV. The Evaluation of'the Quality of Abstracts 92 1. Need for an Evaluation Procedure 92 2. 'Existing Methods of Abstract Evaluation 93 3. Analysis of Previous Evaluation Measures for Specific Uses of Abstracts 96 3.1. The Abstract as'an Alerting Tool 97 3.2. The Abstract as a Retrospective Search Tool . 99 3.3. The Abstract as-the Source of Index Entries 101 3.4. The Abstract as a Data Base for information Storage and Retrieval Systems 101 4. Desiderata of an EvaluaCion Criterion 104 4 t. Importance of Data 105 6. The Relationship'Between Data and Information . 107 6.1. On the Difficulty of Using "Information Content" as a Basis for Evaluation of Abstracts . 110 6.2. On the Usefulness of Data Content as a Basis for Evaluation of Abstracts 110 7. A Two-Step Procedure for the Evaluation of Abstracts 113 7.1. Step 1 114 7.2. Step 2 117 7.2.1. Definition of the Data Coefficient 117 7.2.1.1. Definition of the Units of Dateand Length 124 7.2.1.2. Implementation of the Data Coefficient 1;26 7.2..3. The Representation of Concepts by Name-Relation-Name Patterns 1z8 'e 8. Examples of the Application of the Content Evaluation Criterion 132 8.1. Sample DocUment with Six Possible Abstracts . 132 8.2. Fourteen Abstracts produced by the Abstracting System 144 8.3. Summary of Results of the Experimental-Application of The Data Content Criterion 167 References 169 V. Improvement of the Abstracting System $$ 171 1. Improvement of the Quality of Abstracts through Sentence Modification 171 1.1.
Recommended publications
  • Data ONTAP® 8.2 Commands: Manual Page Reference for 7-Mode, Volume 1
    Data ONTAP® 8.2 Commands: Manual Page Reference For 7-Mode, Volume 1 NetApp, Inc. Telephone: +1 (888) 463-8277 Part Number: 215-07976_A0 495 East Java Drive Fax: +1(408) 822-4501 May 2013 Sunnyvale, CA 94089 Support telephone: +1(888) 4-NETAPP U.S. Web: www.netapp.com Feedback: [email protected] Table of Contents ...................... 1 About the Data ONTAP Commands: Manual Page Reference, Volume 1 .3.... Manual Pages by Section in This Volume and Complete Index of Both Volumes .5.. acpadmin ................... 18 aggr ..................... 20 arp ..................... 41 autosupport ................... 43 backup .................... 53 bmc ..................... 55 bootfs .................... 57 cdpd ..................... 58 cf ..................... 61 charmap .................... 64 cifs ..................... 66 cifs_access ................... 68 cifs_adupdate .................. 70 cifs_audit ................... 71 cifs_branchcache .................. 72 cifs_broadcast .................. 74 cifs_changefilerpwd .7................ 5 cifs_comment ............. ..... 76 cifs_domaininfo .................. 77 cifs_help .................... 79 cifs_homedir ................... 80 cifs_lookup ................... 81 cifs_nbalias ................... 82 cifs_prefdc ................... 83 cifs_resetdc ................... 85 cifs_restart ................... 86 cifs_sessions ................... 87 cifs_setup ................... 91 cifs_shares ................... 93 cifs_sidcache ................... 102 cifs_stat .................... 104 cifs_terminate
    [Show full text]
  • EM316LNXNM-OT Network Manager with Linux
    EM316LNXNM-OT Network Manager with Linux Fiber Driver Optical Multi-Service Platform Published 2012/10/17 15:28:24 P/N 1275005-100 Revision E6 ( -build r21138- ) For EM316LNXNM v4.7 fdr 39 built Oct 16 2012 - 19:07:17 EM316LNXNM-OT Preface Copyright © 2012 MRV Communications, Inc. All rights reserved. No part of the contents of this document may be reproduced in any form or by any other means without written permission from the publisher. Fiber Driver, Media Cross Connect, MegaVision, and other MRV product names and terms belong to MRV Communications or affiliates. All other brand names or trademarks referenced are the property of their respective owners. This document includes electronic links and URLs that may require internet access. Some references may not be obvious on printed pages. The user assumes sole responsibility for applying the information supplied in product documents. MRV Communications reserves the right to make changes to technical specifications and documentation without notice. This document represents the most recent product versions at the time of writing, which may differ from previous releases. To ensure maximum functionality, use the latest software updates and documents. Contact customer support regarding previous product revisions and documents. PN 1275005-100 Rev E6 intro- 2 EM316LNXNM-OT Preface Table of Contents 1. Support and Safety .......................................................................................................... 1 1.1. Customer Support ................................................................................................
    [Show full text]
  • Scripting in Axis Network Cameras and Video Servers
    Scripting in Axis Network Cameras and Video Servers Table of Contents 1 INTRODUCTION .............................................................................................................5 2 EMBEDDED SCRIPTS ....................................................................................................6 2.1 PHP .....................................................................................................................................6 2.2 SHELL ..................................................................................................................................7 3 USING SCRIPTS IN AXIS CAMERA/VIDEO PRODUCTS ......................................8 3.1 UPLOADING SCRIPTS TO THE CAMERA/VIDEO SERVER:...................................................8 3.2 RUNNING SCRIPTS WITH THE TASK SCHEDULER...............................................................8 3.2.1 Syntax for /etc/task.list.....................................................................................................9 3.3 RUNNING SCRIPTS VIA A WEB SERVER..............................................................................11 3.3.1 To enable Telnet support ...............................................................................................12 3.4 INCLUDED HELPER APPLICATIONS ..................................................................................13 3.4.1 The image buffer - bufferd........................................................................................13 3.4.2 sftpclient.........................................................................................................................16
    [Show full text]
  • Managing Clock Synchronization in Oracle® Solaris 11.4
    Managing Clock Synchronization in ® Oracle Solaris 11.4 Part No: E61003 January 2019 Managing Clock Synchronization in Oracle Solaris 11.4 Part No: E61003 Copyright © 2002, 2019, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
    [Show full text]
  • OEP User's Manual
    Omni-EP JK microsystems Omni-EP Manual Unless otherwise noted, this document and the information herein disclosed are proprietary to JK microsystems, Inc. Any person or entity to whom this document is furnished or having possession thereof, by acceptance, assumes custody thereof and agrees that the document is given in confidence and will not be copied or reproduced in whole or in part to meet the pur- poses for which it was delivered. The information in this document is subject to change without notice, and should not be con- strued as a commitment by JK microsystems, Inc. JK microsystems, Inc. will make every effort to inform users of substantive errors. JK microsystems, Inc. disclaims all liability for any loss or damage resulting from the use of this manual or any software described herein, including without limitation contingent, special, or incidental liability. JK microsystems, Inc. recognizes our customer‘s need for a consistent product and will make every effort to provide one. In order to provide the best possible product for all of our custom- ers, we reserve the right to make incremental improvements in our product designs. Omni-EP is a trademark of JK microsystems, Inc. All other brand and product names are trade- marks or registered trademarks of their respective companies. Omni-EP User‘s Manual Version 1.0 Copyright © JK microsystems, Inc. All rights reserved Printed in U.S.A. Document Part No. 94-0034 Published September 2005 2 JK microsystems Omni-EP Manual Limited Warranty JK microsystems, Inc. warrants each Omni-EP to be free from defects in material and work- manship for a period of 90 days from the date of purchase.
    [Show full text]
  • Command Map for 7-Mode Administrators ONTAP 7-Mode Transition Netapp September 12, 2021
    Command map for 7-Mode administrators ONTAP 7-Mode Transition NetApp September 12, 2021 This PDF was generated from https://docs.netapp.com/us-en/ontap-7mode-transition/command- map/reference_how_7_mode_commands_map_to_clustered_ontap_commands.html on September 12, 2021. Always check docs.netapp.com for the latest. Table of Contents Command Map for 7-Mode Administrators. 1 How 7-Mode commands map to ONTAP commands . 1 How 7-Mode options map to ONTAP commands . 37 How 7-Mode configuration files map to clustered Data ONTAP commands . 69 How to interpret the clustered Data ONTAP commands, options, and configuration files maps for 7-Mode administrators. 70 Command Map for 7-Mode Administrators This guide maps 7-Mode commands to their equivalents in ONTAP. How 7-Mode commands map to ONTAP commands You can use the tables provided to find the ONTAP equivalents of 7-Mode commands, with the exception of the options command. The following tables list the ONTAP equivalents of the 7-Mode options command. Information about understanding these tables is also provided. Understanding the 7-Mode to clustered Data ONTAP command map A-E A 7-Mode command ONTAP command acpadmin configure system node run -node {nodename|local} acpadmin configure acpadmin list_all system node run -node {nodename|local} acpadmin list_all acpadmin stats system node run -node {nodename|local} acpadmin stats aggr add aggr add aggr add-disks storage aggregate add-disks aggr create aggr create storage aggregate create aggr destroy aggr delete storage aggregate delete aggr media_scrub
    [Show full text]
  • Sun Blade 6000 Ethernet Switched NEM 24P 10Gbe Program Documentation
    Sun Blade 6000 Ethernet Switched NEM 24p 10GbE Program Documentation Third Party Licenses and Notices Part No.: E26812-01 November 2011 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Oracle Utilities Network Management System Installation Guide Release 2.4.0.1.0 F17283-01
    Oracle Utilities Network Management System Installation Guide Release 2.4.0.1.0 F17283-01 September 2019 Oracle Utilities Network Management System Installation Guide, Release 2.4.0.1.0 F17283-01 Copyright © 1991, 2019 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial computer software” pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/ or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Learning Embedded Linux Through the File System: a Top-Down Approach
    Learning embedded Linux through the file system: A top-down approach Jason Kridner, [email protected] June 8, 2011, 10:10AM ESC Chicago room 34 http://beagleboard.org/linux_education Abstract Typical introductions to embedded Linux focus on complex tasks, like building device drivers, that are highly desired by at least some people working on your Linux product team. What about the rest of us that simply want to build a quick understanding of how to do some of the simple tasks that are trivial in microcontrollers without using operating systems, like accessing GPIO pins and performing I2C or SPI serial communications? This class takes a quick tops-down overview from the perspective of an electrical engineer looking to take advantage of the latest in GUI building technologies, like Android, Qt, and HTML5, without completely losing access to the underlying hardware for simple system integration tasks. Getting started Much to learn ◦ I‟m used to microcontrollers: just give me the datasheet with register definitions and set me free! Training on boot & device drivers useful ◦ Often geared more at system bring-up ◦ What about the everyday user? ◦ Where is that abstraction benefit? Let‟s just walk a working system Kernel.org documentation http://www.kernel.org/doc/ Documentation extracted from the Linux kernel and mirrored on the web where Google can find it: ◦ Documentation - Text files in the kernel source tarball's Documentation subdirectory. ◦ htmldocs - Kernel Documentation maintained in docbook format (output of "make htmldocs"). ◦ Menuconfig - help text for each kernel configuration option (from kconfig source). ◦ README various README files scattered around Linux kernel source ◦ RFC - List of IETF RFCs referred to by kernel source files.
    [Show full text]
  • Linux, Shell Programming and Perl As Pdf File
    Linux, Shell Programing and Perl by Willi-Hans Steeb, Gert Cronje and Yorick Hardy International School for Scientific Computing Contents 1 Linux Basics 1 1.1 Some Basic Commands . 1 1.2 Working with Files and Directories . 10 1.2.1 Introduction . 10 1.2.2 The Home Directory and Path Names . 11 1.2.3 Important Directories in the Linux File System . 13 1.2.4 Basic Files and Directories Commands . 14 1.2.5 File Name Substitution . 31 1.3 Standard Input/Output, and I/O Redirection . 35 2 Linux Commands 43 3 Advanced Linux 73 3.1 The Unix File System . 73 3.2 Mounting and Unmounting . 76 3.3 MTools Package . 81 3.4 Swap Space and the Loopback Device . 82 3.5 Network File-System . 83 3.6 Linuxconf . 84 3.7 Compressed Files . 85 3.8 The vi and emacs Editors . 88 3.8.1 vi Editor . 88 3.8.2 emacs Editor . 96 3.9 Programming Languages . 99 3.9.1 C and C++ Compiler . 99 3.9.2 Perl . 101 3.9.3 Lisp . 102 3.9.4 Java . 103 4 Linux and Networking 105 4.1 Introduction . 105 4.2 Basic Commands . 106 4.3 email . 116 4.4 ftp Commands . 122 4.5 Telnet . 125 i 4.6 Remote Shell . 127 4.7 Web . 128 4.8 INETD and Socket Programming . 129 5 Shell Programming 133 5.1 What is a shell . 133 5.2 The Shell as a Programming Language . 137 5.2.1 Creating a Script . 138 5.2.2 Making a Script executable .
    [Show full text]
  • Scripting in Axis Network Cameras and Video Servers
    Scripting in Axis Network Cameras and Video Servers Table of Contents 1 INTRODUCTION .............................................................................................................5 2 EMBEDDED SCRIPTS ....................................................................................................6 2.1 PHP .....................................................................................................................................6 2.2 SHELL ..................................................................................................................................7 3 USING SCRIPTS IN AXIS CAMERA/VIDEO PRODUCTS ......................................8 3.1 UPLOADING SCRIPTS TO THE CAMERA/VIDEO SERVER:...................................................8 3.2 RUNNING SCRIPTS WITH THE TASK SCHEDULER...............................................................8 3.2.1 Syntax for /etc/task.list.....................................................................................................9 3.3 RUNNING SCRIPTS VIA A WEB SERVER..............................................................................11 3.3.1 To enable Telnet support ...............................................................................................12 3.4 INCLUDED HELPER APPLICATIONS ..................................................................................13 3.4.1 The image buffer - bufferd........................................................................................13 3.4.2 sftpclient.........................................................................................................................16
    [Show full text]
  • Runtime System
    SCO®TCPIIP Runtime System for SCO®UNIX ®Systems User's and Administrator's Guide sca®TCP/IP Runtitne Systetn for sca® UNIX® System.s User's and Administrator's Guide © 1983-1992 The Santa Cruz Operation, Inc. © 1980-1992 Microsoft Corporation. © 1989-1992 UNIX System Laboratories, Inc. All Rights Reserved. No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any human or computer language, in any form or by any means, electronic, mechani­ cal, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of the copyright owner, The Santa Cruz Operation, Inc., 400 Encinal, Santa Cruz, California, 95060, U.S.A. Copyright infringement is a serious matter under the United States and foreign Copyright Laws. The copyrighted software that accompanies this manual is licensed to the End User only for use in strict accordance with the End User License Agreement, which should be read carefully before com­ mencing use of the software. Information in this document is subject to change without notice and does not represent a commitment on the part of The Santa Cruz Operation, Inc. SCO OPEN DESKTOP Software is commercial computer software and, together with any related documentation, is subject to the restrictions on U.S. Government use as set forth below. If this procurement is for a DOD agency, the following DFAR Restricted Rights Legend applies: RESTRICTED RIGHTS LEGEND: Use, duplication or disclosure by the Government is subject to restrictions as set forth in subpararaph (c)(1)(ii) of rights in Technical Data and Computer Software Clause at DFARS 252.227-7013.
    [Show full text]