DOCSLIB.ORG

Release 0.11 Todd Gamblin

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Release 0.11 Todd Gamblin Spack Documentation Release 0.11 Todd Gamblin Feb 07, 2018 Basics 1 Feature Overview 3 1.1 Simple package installation.......................................3 1.2 Custom versions & configurations....................................3 1.3 Customize dependencies.........................................4 1.4 Non-destructive installs.........................................4 1.5 Packages can peacefully coexist.....................................4 1.6 Creating packages is easy........................................4 2 Getting Started 7 2.1 Prerequisites...............................................7 2.2 Installation................................................7 2.3 Compiler configuration..........................................9 2.4 Vendor-Specific Compiler Configuration................................ 13 2.5 System Packages............................................. 16 2.6 Utilities Configuration.......................................... 18 2.7 GPG Signing............................................... 20 2.8 Spack on Cray.............................................. 21 3 Basic Usage 25 3.1 Listing available packages........................................ 25 3.2 Installing and uninstalling........................................ 42 3.3 Seeing installed packages........................................ 44 3.4 Specs & dependencies.......................................... 46 3.5 Virtual dependencies........................................... 50 3.6 Extensions & Python support...................................... 53 3.7 Filesystem requirements......................................... 56 3.8 Getting Help............................................... 57 4 Workflows 61 4.1 Definitions................................................ 61 4.2 Building Packages............................................ 62 4.3 Running Binaries from Packages.................................... 64 4.4 Developing Software with Spack.................................... 69 4.5 Using Spack on Travis-CI........................................ 74 4.6 Using Spack to Create Docker Images.................................. 76 4.7 Upstream Bug Fixes........................................... 78 i 5 Tutorial: Spack 101 81 5.1 Basic Installation Tutorial........................................ 82 5.2 Configuration Tutorial.......................................... 123 5.3 Package Creation Tutorial........................................ 139 5.4 Spack Package Build Systems...................................... 150 5.5 Advanced Topics in Packaging...................................... 184 5.6 Module Files............................................... 193 6 Known Issues 223 6.1 Default variants are not taken into account during concretization.................... 223 6.2 Variants are not properly forwarded to dependencies.......................... 223 6.3 spack setup doesn’t work...................................... 224 7 Configuration Files in Spack 225 7.1 YAML Format.............................................. 225 7.2 Configuration Scopes........................................... 226 7.3 Platform-specific scopes......................................... 226 7.4 Scope precedence............................................ 227 7.5 Config file variables........................................... 229 8 Basic settings in config.yaml 231 8.1 install_tree ............................................ 232 8.2 install_hash_length and install_path_scheme ..................... 233 8.3 module_roots ............................................ 233 8.4 build_stage ............................................. 233 8.5 source_cache ............................................ 234 8.6 misc_cache .............................................. 234 8.7 verify_ssl .............................................. 234 8.8 checksum ................................................ 234 8.9 dirty .................................................. 234 8.10 build_jobs .............................................. 235 9 Build customization 237 9.1 External Packages............................................ 237 9.2 Concretization Preferences........................................ 238 10 Mirrors 241 10.1 spack mirror ............................................ 242 10.2 spack mirror create ....................................... 242 10.3 spack mirror add ......................................... 243 10.4 spack mirror list ........................................ 244 10.5 spack mirror remove ....................................... 244 10.6 Mirror precedence............................................ 244 10.7 Local Default Cache........................................... 244 11 Modules 245 11.1 Using module files via Spack...................................... 245 11.2 Module file customization........................................ 249 11.3 Maintaining Module Files........................................ 255 12 Package Repositories 259 12.1 repos.yaml .............................................. 260 12.2 Namespaces............................................... 260 12.3 Overriding built-in packages....................................... 261 12.4 spack repo .............................................. 263 ii 12.5 Repo namespaces and Python...................................... 265 13 Build caches 267 13.1 Creating build cache files........................................ 267 13.2 Finding or installing build cache files.................................. 267 13.3 Relocation................................................ 268 13.4 spack buildcache ......................................... 268 14 Command Index 271 15 Package List 273 16 Contribution Guide 275 16.1 Continuous Integration.......................................... 275 16.2 Coverage................................................. 279 16.3 Git Workflows.............................................. 280 17 Packaging Guide 285 17.1 Creating & editing packages....................................... 285 17.2 Naming & directory structure...................................... 288 17.3 Trusted Downloads............................................ 290 17.4 Versions and fetching.......................................... 290 17.5 Finding new versions........................................... 294 17.6 Fetching from code repositories..................................... 296 17.7 Resources (expanding extra tarballs)................................... 298 17.8 Licensed software............................................ 298 17.9 Patches.................................................. 300 17.10 Handling RPATHs............................................ 303 17.11 Parallel builds.............................................. 303 17.12 Dependencies............................................... 304 17.13 Conflicts................................................. 308 17.14 Extensions................................................ 308 17.15 Virtual dependencies........................................... 311 17.16 Abstract & concrete specs........................................ 312 17.17 Conflicting Specs............................................. 314 17.18 Implementing the installation procedure................................. 315 17.19 The build environment.......................................... 317 17.20 Spec objects............................................... 322 17.21 Compiler wrappers............................................ 325 17.22 MPI support in Spack.......................................... 326 17.23 Checking an installation......................................... 328 17.24 File manipulation functions....................................... 329 17.25 Style guidelines for packages...................................... 331 17.26 Packaging workflow commands..................................... 331 17.27 Graphing dependencies......................................... 333 17.28 Interactive shell support......................................... 338 18 Developer Guide 343 18.1 Overview................................................. 343 18.2 Directory Structure............................................ 344 18.3 Code Structure.............................................. 345 18.4 Spec objects............................................... 346 18.5 Package objects............................................. 346 18.6 Stage objects............................................... 347 18.7 Writing commands............................................ 347 iii 18.8 Unit tests................................................. 347 18.9 Unit testing................................................ 347 18.10 Developer commands.......................................... 347 18.11 Profiling................................................. 350 19 spack package 351 19.1 Subpackages............................................... 351 19.2 Submodules............................................... 451 19.3 spack.abi module............................................. 451 19.4 spack.architecture module........................................ 451 19.5 spack.binary_distribution module.................................... 453 19.6 spack.build_environment module.................................... 455 19.7 spack.compiler module.......................................... 457 19.8 spack.concretize module......................................... 458 19.9 spack.config module........................................... 459 19.10 spack.database module.......................................... 461 19.11 spack.dependency module........................................ 463 19.12
Load more

Recommended publications
  • Armadillo C++ Library
    Armadillo: a template-based C++ library for linear algebra Conrad Sanderson and Ryan Curtin Abstract The C++ language is often used for implementing functionality that is performance and/or resource sensitive. While the standard C++ library provides many useful algorithms (such as sorting), in its current form it does not provide direct handling of linear algebra (matrix maths). Armadillo is an open source linear algebra library for the C++ language, aiming towards a good balance between speed and ease of use. Its high-level application programming interface (function syntax) is deliberately similar to the widely used Matlab and Octave languages [4], so that mathematical operations can be expressed in a familiar and natural manner. The library is useful for algorithm development directly in C++, or relatively quick conversion of research code into production environments. Armadillo provides efficient objects for vectors, matrices and cubes (third order tensors), as well as over 200 associated functions for manipulating data stored in the objects. Integer, floating point and complex numbers are supported, as well as dense and sparse storage formats. Various matrix factorisations are provided through integration with LAPACK [3], or one of its high performance drop-in replacements such as Intel MKL [6] or OpenBLAS [9]. It is also possible to use Armadillo in conjunction with NVBLAS to obtain GPU-accelerated matrix multiplication [7]. Armadillo is used as a base for other open source projects, such as MLPACK, a C++ library for machine learning and pattern recognition [2], and RcppArmadillo, a bridge between the R language and C++ in order to speed up computations [5].
    [Show full text]
  • Cellular Sheaf Cohomology in Polymake Arxiv:1612.09526V1
    Cellular sheaf cohomology in Polymake Lars Kastner, Kristin Shaw, Anna-Lena Winz July 9, 2018 Abstract This chapter provides a guide to our polymake extension cellularSheaves. We first define cellular sheaves on polyhedral complexes in Euclidean space, as well as cosheaves, and their (co)homologies. As motivation, we summarise some results from toric and tropical geometry linking cellular sheaf cohomologies to cohomologies of algebraic varieties. We then give an overview of the structure of the extension cellularSheaves for polymake. Finally, we illustrate the usage of the extension with examples from toric and tropical geometry. 1 Introduction n Given a polyhedral complex Π in R , a cellular sheaf (of vector spaces) on Π associates to every face of Π a vector space and to every face relation a map of the associated vector spaces (see Definition 2). Just as with usual sheaves, we can compute the cohomology of cellular sheaves (see Definition 5). The advantage is that cellular sheaf cohomology is the cohomology of a chain complex consisting of finite dimensional vector spaces (see Definition 3). Polyhedral complexes often arise in algebraic geometry. Moreover, in some cases, invariants of algebraic varieties can be recovered as cohomology of certain cellular sheaves on polyhedral complexes. Our two major classes of examples come from toric and tropical geometry and are presented in Section 2.2. We refer the reader to [9] for a guide to toric geometry and polytopes. For an introduction to tropical geometry see [4], [20]. The main motivation for this polymake extension was to implement tropical homology, as introduced by Itenberg, Katzarkov, Mikhalkin, and Zharkov in [15].
    [Show full text]
  • Using the GNU Compiler Collection (GCC)
    Using the GNU Compiler Collection (GCC) Using the GNU Compiler Collection by Richard M. Stallman and the GCC Developer Community Last updated 23 May 2004 for GCC 3.4.6 For GCC Version 3.4.6 Published by: GNU Press Website: www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 59 Temple Place Suite 330 Tel 617-542-5942 Boston, MA 02111-1307 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being \GNU General Public License" and \Funding Free Software", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled \GNU Free Documentation License". (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ...................................... 1 1 Programming Languages Supported by GCC ............ 3 2 Language Standards Supported by GCC ............... 5 3 GCC Command Options .........................
    [Show full text]
  • Rcppmlpack: R Integration with MLPACK Using Rcpp
    RcppMLPACK: R integration with MLPACK using Rcpp Qiang Kou [email protected] April 20, 2020 1 MLPACK MLPACK[1] is a C++ machine learning library with emphasis on scalability, speed, and ease-of-use. It outperforms competing machine learning libraries by large margins, for detailed results of benchmarking, please refer to Ref[1]. 1.1 Input/Output using Armadillo MLPACK uses Armadillo as input and output, which provides vector, matrix and cube types (integer, floating point and complex numbers are supported)[2]. By providing Matlab-like syntax and various matrix decompositions through integration with LAPACK or other high performance libraries (such as Intel MKL, AMD ACML, or OpenBLAS), Armadillo keeps a good balance between speed and ease of use. Armadillo is widely used in C++ libraries like MLPACK. However, there is one point we need to pay attention to: Armadillo matrices in MLPACK are stored in a column-major format for speed. That means observations are stored as columns and dimensions as rows. So when using MLPACK, additional transpose may be needed. 1.2 Simple API Although MLPACK relies on template techniques in C++, it provides an intuitive and simple API. For the standard usage of methods, default arguments are provided. The MLPACK paper[1] provides a good example: standard k-means clustering in Euclidean space can be initialized like below: 1 KMeans<> k(); Listing 1: k-means with all default arguments If we want to use Manhattan distance, a different cluster initialization policy, and allow empty clusters, the object can be initialized with additional arguments: 1 KMeans<ManhattanDistance, KMeansPlusPlusInitialization, AllowEmptyClusters> k(); Listing 2: k-means with additional arguments 1 1.3 Available methods in MLPACK Commonly used machine learning methods are all implemented in MLPACK.
    [Show full text]
  • The GNU Configure and Build System
    The GNU configure and build system Ian Lance Taylor Copyright c 1998 Cygnus Solutions Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the con- ditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. i Table of Contents 1 Introduction ............................... 1 1.1 Goals................................................... 1 1.2 Tools ................................................... 1 1.3 History ................................................. 1 1.4 Building ................................................ 2 2 Getting Started............................ 3 2.1 Write configure.in ....................................... 4 2.2 Write Makefile.am ....................................... 6 2.3 Write acconfig.h......................................... 7 2.4 Generate files ........................................... 8 2.5 Example................................................ 8 2.5.1 First Try....................................... 9 2.5.2 Second Try.................................... 10 2.5.3 Third
    [Show full text]
  • Release Notes for Fedora 20
    Fedora 20 Release Notes Release Notes for Fedora 20 Edited by The Fedora Docs Team Copyright © 2013 Fedora Project Contributors. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries. All other trademarks are the property of their respective owners.
    [Show full text]
  • Code Structure by Miklos Vajna Senior Software Engineer at Collabora Productivity 2017-10-11
    LibreOffice: Code Structure By Miklos Vajna Senior Software Engineer at Collabora Productivity 2017-10-11 @CollaboraOffice www.CollaboraOffice.com About Miklos ● From Hungary ● More blurb: http://vmiklos.hu/ ● Google Summer of Code 2010/2011 ● Rewrite of the Writer RTF import/export ● Writer developer since 2012 ● Contractor at Collabora since 2013 LibreOffice Conference 2017, Rome | Miklos Vajna 2 / 30 Thanks ● This is an updated version of Michael Meeks’ talk from last year LibreOffice Conference 2017, Rome | Miklos Vajna 3 / 30 Overview ● Code-base overview ● Internal core modules, internal leaf ● Ignoring externals ● Building / packaging: gnumake, scp2 ● Code organisation, git bits ● Keep in mind: this is a 20 years old code-base ● The quality is much better than you would expect after knowing its age ● Things continue to improve over time LibreOffice Conference 2017, Rome | Miklos Vajna 4 / 30 Module overview lowest level Internal non-leaf modules: UNO modules ● Module = toplevel dir ● make dumps-deps-png ● Each module has a README ● e.g. sal/README ● sal: at the bottom ● The system abstraction layer ● tools is an obsolete internal (more or less) duplication of this ● salhelper: wrapper code around sal, also part of the URE LibreOffice Conference 2017, Rome | Miklos Vajna 6 / 30 What is the Uno Runtime Environment (URE)? ● We’ll come to UNO in detail a bit later, but for now: ● Uno Runtime Environment ● See also JRE, Java Runtime Env. ● Belongs to the idea that UNO would be reused somewhere else ● Provides an API/ABI-stable abstraction layer for the suite URE ● Allows writing C++ extensions ● Modify carefully: ● Should not change the ABI ● ABI control via C .map files LibreOffice Conference 2017, Rome | Miklos Vajna 7 / 30 UNO modules ● store: legacy .rdb format ● registry: UNO type regisistry ● unoidl: a .idl file compiler ● cppu: C++ UNO ● Implements basic UNO types and infrastructure for C++, e.g.
    [Show full text]
  • Easybuild Documentation Release 20210907.0
    EasyBuild Documentation Release 20210907.0 Ghent University Tue, 07 Sep 2021 08:55:41 Contents 1 What is EasyBuild? 3 2 Concepts and terminology 5 2.1 EasyBuild framework..........................................5 2.2 Easyblocks................................................6 2.3 Toolchains................................................7 2.3.1 system toolchain.......................................7 2.3.2 dummy toolchain (DEPRECATED) ..............................7 2.3.3 Common toolchains.......................................7 2.4 Easyconfig files..............................................7 2.5 Extensions................................................8 3 Typical workflow example: building and installing WRF9 3.1 Searching for available easyconfigs files.................................9 3.2 Getting an overview of planned installations.............................. 10 3.3 Installing a software stack........................................ 11 4 Getting started 13 4.1 Installing EasyBuild........................................... 13 4.1.1 Requirements.......................................... 14 4.1.2 Using pip to Install EasyBuild................................. 14 4.1.3 Installing EasyBuild with EasyBuild.............................. 17 4.1.4 Dependencies.......................................... 19 4.1.5 Sources............................................. 21 4.1.6 In case of installation issues. .................................. 22 4.2 Configuring EasyBuild.......................................... 22 4.2.1 Supported configuration
    [Show full text]
  • The Glib/GTK+ Development Platform
    The GLib/GTK+ Development Platform A Getting Started Guide Version 0.8 Sébastien Wilmet March 29, 2019 Contents 1 Introduction 3 1.1 License . 3 1.2 Financial Support . 3 1.3 Todo List for this Book and a Quick 2019 Update . 4 1.4 What is GLib and GTK+? . 4 1.5 The GNOME Desktop . 5 1.6 Prerequisites . 6 1.7 Why and When Using the C Language? . 7 1.7.1 Separate the Backend from the Frontend . 7 1.7.2 Other Aspects to Keep in Mind . 8 1.8 Learning Path . 9 1.9 The Development Environment . 10 1.10 Acknowledgments . 10 I GLib, the Core Library 11 2 GLib, the Core Library 12 2.1 Basics . 13 2.1.1 Type Definitions . 13 2.1.2 Frequently Used Macros . 13 2.1.3 Debugging Macros . 14 2.1.4 Memory . 16 2.1.5 String Handling . 18 2.2 Data Structures . 20 2.2.1 Lists . 20 2.2.2 Trees . 24 2.2.3 Hash Tables . 29 2.3 The Main Event Loop . 31 2.4 Other Features . 33 II Object-Oriented Programming in C 35 3 Semi-Object-Oriented Programming in C 37 3.1 Header Example . 37 3.1.1 Project Namespace . 37 3.1.2 Class Namespace . 39 3.1.3 Lowercase, Uppercase or CamelCase? . 39 3.1.4 Include Guard . 39 3.1.5 C++ Support . 39 1 3.1.6 #include . 39 3.1.7 Type Definition . 40 3.1.8 Object Constructor . 40 3.1.9 Object Destructor .
    [Show full text]
  • Art-Workbook-V0 84
    Intensity Frontier Common Offline Documentation: art Workbook and Users Guide Alpha Release 0.84 August 18, 2014 This version of the documentation is written for version v0_00_27 of the art-workbook code. Scientific Computing Division Future Programs and Experiments Department Scientific Software Infrastructure Group Principal Author: Rob Kutschke Editor: Anne Heavey art Developers: L. Garren, C. Green, J. Kowalkowski, M. Paterno and P. Russo 1 2 List of Chapters Detailed Table of Contents iv List of Figures xx List of Tables xxii List of Code and Output Listings xxii art Glossary xxvii I Introduction 1 1 How to Read this Documentation 2 2 Conventions Used in this Documentation 4 3 Introduction to the art Event Processing Framework 7 4 Unix Prerequisites 34 5 Site-Specific Setup Procedure 45 i 6 Get your C++ up to Speed 47 7 Using External Products in UPS 107 II Workbook 119 8 Preparation for Running the Workbook Exercises 120 9 Exercise 1: Running Pre-built art Modules 124 10 Exercise 2: Building and Running Your First Module 163 11 General Setup for Login Sessions 220 12 Keeping Up to Date with Workbook Code and Documentation 222 13 Exercise 3: Some other Member Functions of Modules 228 14 Exercise 4: A First Look at Parameter Sets 240 15 Exercise 5: Making Multiple Instances of a Module 265 16 Exercise 6: Accessing Data Products 272 17 Exercise 7: Making a Histogram 291 18 Exercise 8: Looping Over Collections 317 19 3D Event Displays 341 20 Troubleshooting 377 ii III User’s Guide 379 21 Obtaining Credentials to Access Fermilab Computing Resources 380 22 git 382 23 art Run-time and Development Environments 391 24 art Framework Parameters 399 25 Job Configuration in art: FHiCL 405 IV Appendices 424 A art Completion Codes 425 B Viewing and Printing Figure Files 428 C CLHEP 430 D Include Guards 446 V Index 448 Index 449 iii Detailed Table of Contents Detailed Table of Contents iv List of Figures xx List of Tables xxii List of Code and Output Listings xxii art Glossary xxvii I Introduction 1 1 How to Read this Documentation 2 1.1 If you are new to HEP Software..
    [Show full text]
  • Empirical Comparison of Scons and GNU Make
    Großer Beleg Empirical Comparison of SCons and GNU Make Ludwig Hähne August 21, 2008 Technical University Dresden Department of Computer Science Institute for System Architecture Chair for Operating Systems Professor: Prof. Dr. rer. nat. Hermann Härtig Tutor: Dipl.-Inf. Norman Feske Dipl.-Inf. Christian Helmuth Erklärung Hiermit erkläre ich, dass ich diese Arbeit selbstständig erstellt und keine anderen als die angegebenen Hilfsmittel benutzt habe. Dresden, den 26. Juni 2008 Ludwig Hähne Abstract Build systems are an integral part of every software developer’s tool kit. Next to the well-known Make build system, numerous alternative solutions emerged during the last decade. Even though the new systems introduced superior concepts like content signa- tures and promise to provide better build accuracy, Make is still the de facto standard. This paper examines GNU Make and SCons as representatives of two conceptually distinct approaches to conduct software builds. General build-system concepts and their respective realizations are discussed. The performance and scalability are empirically evaluated by confronting the two competitors with comparable real and synthetic build tasks. V Contents 1 Introduction 1 2 Background 3 2.1 Design Goals . .3 2.1.1 Convenience . .3 2.1.2 Correctness . .3 2.1.3 Performance . .3 2.1.4 Scalability . .4 2.2 Software Rebuilding . .4 2.2.1 Dependency analysis . .4 2.2.1.1 File signatures . .4 2.2.1.2 Fine grained dependencies . .5 2.2.1.3 Dependency declaration . .5 2.2.1.4 Dependency types . .5 2.2.2 Build infrastructure . .6 2.2.3 Command scheduling . .6 2.3 Build System Features .
    [Show full text]
  • Zenworks Agent Reference
    ZENworks® 2017 Update 4 ZENworks Agent Reference January 2019 Legal Notice For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.novell.com/company/legal/. © Copyright 2008 - 2019 Micro Focus or one of its affiliates. The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. About This Guide This ZENworks Agent Reference provides information to help you perform administrative tasks related to the ZENworks Agent. The information in this guide is organized as follows: Chapter 1, “Introduction,” on page 7 Chapter 2, “Viewing the Version of the ZENworks Agent Software and Modules on a Device,” on page 9 Chapter 3, “Searching for Devices that Have a Specified Version of the ZENworks Agent,” on page 11 Chapter 4, “Configuring ZENworks Agent Settings after Deployment,” on page 13 Chapter 5, “Configuring ZENworks Explorer,” on page 29 Chapter 6, “Removing the ZENworks Pre-Agent from a Device,” on page 31 Chapter 7, “Configuring the System Update Behavior of the ZENworks Agent,” on page 33 Chapter 8, “Customizing the Look and Feel of the ZENworks Icon,” on page 35 Chapter 9, “Troubleshooting the ZENworks Agent,” on page 37 Appendix A, “RPMs for the Linux ZENworks Agent,” on page 45 Audience This guide is intended for ZENworks administrators.
    [Show full text]