DOCSLIB.ORG

Platform LSF Configuration Reference Chapter 1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Platform LSF Configuration Reference Chapter 1 Platform LSF Version 9 Release 1.2 Configuration Reference SC27-5306-02 Platform LSF Version 9 Release 1.2 Configuration Reference SC27-5306-02 Note Before using this information and the product it supports, read the information in “Notices” on page 631. First edition This edition applies to version 9, release 1 of IBM Platform LSF (product number 5725G82) and to all subsequent releases and modifications until otherwise indicated in new editions. Significant changes or additions to the text and illustrations are indicated by a vertical line (|) to the left of the change. If you find an error in any Platform Computing documentation, or you have a suggestion for improving it, please let us know. Send your suggestions, comments and questions to the following email address: [email protected] Be sure include the publication title and order number, and, if applicable, the specific location of the information about which you have comments (for example, a page number or a browser URL). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 1992, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Configuration Files .....1 lsf.licensescheduler ...........502 cshrc.lsf and profile.lsf ...........1 lsf.shared ...............554 dc_conf.cluster_name.xml parameters ......9 lsf.sudoers ..............560 hosts ................16 lsf.task ...............566 install.config ..............18 setup.config ..............569 lim.acct ................30 slave.config ..............572 lsb.acct ................31 lsb.applications .............40 Chapter 2. Environment Variables . 579 lsb.events ...............86 Environment variables set for job execution . 579 lsb.hosts ...............126 Environment variables for resize notification lsb.modules ..............142 command ..............580 lsb.params ..............146 Environment variables for session scheduler lsb.queues ..............224 (ssched) ...............581 lsb.resources..............286 Environment variable reference .......582 lsb.serviceclasses ............320 lsb.users ...............330 Notices ..............631 lsf.acct................338 Trademarks ..............633 lsf.cluster ...............340 Privacy policy considerations ........633 lsf.conf ...............361 © Copyright IBM Corp. 1992, 2013 iii iv Platform LSF Configuration Reference Chapter 1. Configuration Files Important: Specify any domain names in all uppercase letters in all configuration files. cshrc.lsf and profile.lsf About cshrc.lsf and profile.lsf The user environment shell files cshrc.lsf and profile.lsf set the LSF operating environment on an LSF host. They define machine-dependent paths to LSF commands and libraries as environment variables: v cshrc.lsf sets the C shell (csh or tcsh) user environment for LSF commands and libraries v profile.lsf sets and exports the Bourne shell/Korn shell (sh, ksh,orbash) user environment for LSF commands and libraries Tip: LSF Administrators should make sure that cshrc.lsf or profile.lsf are available for users to set the LSF environment variables correctly for the host type running LSF. Location cshrc.lsf and profile.lsf are created by lsfinstall during installation. After installation, they are located in LSF_CONFDIR (LSF_TOP/conf/). Format cshrc.lsf and profile.lsf are conventional UNIX shell scripts: v cshrc.lsf runs under /bin/csh v profile.lsf runs under /bin/sh What cshrc.lsf and profile.lsf do cshrc.lsf and profile.lsf determine the binary type (BINARY_TYPE) of the host and set environment variables for the paths to the following machine-dependent LSF directories, according to the LSF version (LSF_VERSION) and the location of the top-level installation directory (LSF_TOP) defined at installation: v LSF_BINDIR v LSF_SERVERDIR v LSF_LIBDIR v XLSF_UIDDIR cshrc.lsf and profile.lsf also set the following user environment variables: v LSF_ENVDIR v LD_LIBRARY_PATH v PATH to include the paths to: – LSF_BINDIR – LSF_SERVERDIR © Copyright IBM Corp. 1992, 2013 1 cshrc.lsf and profile.lsf v MANPATH to include the path to the LSF man pages If EGO is enabled If EGO is enabled in the LSF cluster (LSF_ENABLE_EGO=Y and LSF_EGO_ENVDIR are defined in lsf.conf), cshrc.lsf and profile.lsf set the following environment variables. v EGO_BINDIR v EGO_CONFDIR v EGO_ESRVDIR v EGO_LIBDIR v EGO_LOCAL_CONFDIR v EGO_SERVERDIR v EGO_TOP Setting the LSF environment with cshrc.lsf and profile.lsf Before using LSF, you must set the LSF execution environment. After logging on to an LSF host, use one of the following shell environment files to set your LSF environment: v For example, in csh or tcsh: source /usr/lsf/lsf_9/conf/cshrc.lsf v For example, in sh, ksh,orbash: . /usr/lsf/lsf_9/conf/profile.lsf Making your cluster available to users with cshrc.lsf and profile.lsf To set the LSF user environment, run one of the following two shell files: v LSF_CONFDIR/cshrc.lsf (for csh, tcsh) v LSF_CONFDIR/profile.lsf (for sh, ksh,orbash) Tip: LSF administrators should make sure all LSF users include one of these files at the end of their own .cshrc or .profile file, or run one of these two files before using LSF. For csh or tcsh Add cshrc.lsf to the end of the .cshrc file for all users: v Copy the cshrc.lsf file into .cshrc,or v Add a line similar to the following to the end of .cshrc: source /usr/lsf/lsf_9/conf/cshrc.lsf After running cshrc.lsf, use setenv to see the environment variable settings. For example: setenv PATH=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/bin ... MANPATH=/usr/lsf/lsf_9/9.1.2/man 2 Platform LSF Configuration Reference cshrc.lsf and profile.lsf ... LSF_BINDIR=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/bin LSF_SERVERDIR=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/etc LSF_LIBDIR=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/lib LD_LIBRARY_PATH=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/lib XLSF_UIDDIR=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/lib/uid LSF_ENVDIR=/usr/lsf/lsf_9/conf Note: These variable settings are an example only. Your system may set additional variables. For sh, ksh, or bash Add profile.lsf to the end of the .profile file for all users: v Copy the profile.lsf file into .profile,or v Add a line similar to following to the end of .profile: . /usr/lsf/lsf_9/conf/profile.lsf After running profile.lsf, use the setenv command to see the environment variable settings. For example: setenv ... LD_LIBRARY_PATH=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/lib LSF_BINDIR=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/bin LSF_ENVDIR=/usr/lsf/lsf_9/conf LSF_LIBDIR=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/lib LSF_SERVERDIR=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/etc MANPATH=/usr/lsf/lsf_9/9.1.2/man PATH=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/bin ... XLSF_UIDDIR=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/lib/uid ... Note: These variable settings are an example only. Your system may set additional variables. cshrc.lsf and profile.lsf on dynamically added LSF slave hosts Dynamically added LSF hosts that will not be master candidates are slave hosts. Each dynamic slave host has its own LSF binaries and local lsf.conf and shell environment scripts (cshrc.lsf and profile.lsf). LSF environment variables set by cshrc.lsf and profile.lsf LSF_BINDIR Syntax LSF_BINDIR=dir Description Directory where LSF user commands are installed. Chapter 1. Configuration Files 3 cshrc.lsf and profile.lsf Examples v Set in csh and tcsh by cshrc.lsf: setenv LSF_BINDIR /usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/bin v Set and exported in sh, ksh,orbash by profile.lsf: LSF_BINDIR=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/bin Values v In cshrc.lsf for csh and tcsh: setenv LSF_BINDIR $LSF_TOP/$LSF_VERSION/$BINARY_TYPE/bin v Set and exported in profile.lsf for sh, ksh,orbash: LSF_BINDIR=$LSF_TOP/$LSF_VERSION/$BINARY_TYPE/bin LSF_ENVDIR Syntax LSF_ENVDIR=dir Description Directory containing the lsf.conf file. By default, lsf.conf is installed by creating a shared copy in LSF_CONFDIR and adding a symbolic link from /etc/lsf.conf to the shared copy. If LSF_ENVDIR is set, the symbolic link is installed in LSF_ENVDIR/lsf.conf. The lsf.conf file is a global environment configuration file for all LSF services and applications. The LSF default installation places the file in LSF_CONFDIR. Examples v Set in csh and tcsh by cshrc.lsf: setenv LSF_ENVDIR /usr/lsf/lsf_9/conf v Set and exported in sh, ksh,orbash by profile.lsf: LSF_ENVDIR=/usr/lsf/lsf_9/conf Values v In cshrc.lsf for csh and tcsh: setenv LSF_ENVDIR $LSF_TOP/conf v Set and exported in profile.lsf for sh, ksh,orbash: LSF_ENVDIR=$LSF_TOP/conf LSF_LIBDIR Syntax LSF_LIBDIR=dir Description Directory where LSF libraries are installed. Library files are shared by all hosts of the same type. 4 Platform LSF Configuration Reference cshrc.lsf and profile.lsf Examples v Set in csh and tcsh by cshrc.lsf: setenv LSF_LIBDIR /usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/lib v Set and exported in sh, ksh,orbash by profile.lsf: LSF_LIBDIR=/usr/lsf/lsf_9/9.1.2/linux2.6-glibc2.3-x86/lib Values v In cshrc.lsf for csh and tcsh: setenv LSF_LIBDIR $LSF_TOP/$LSF_VERSION/$BINARY_TYPE/lib v Set and exported in profile.lsf for sh, ksh,orbash: LSF_LIBDIR=$LSF_TOP/$LSF_VERSION/$BINARY_TYPE/lib LSF_SERVERDIR Syntax LSF_SERVERDIR=dir Description Directory where LSF server binaries and shell scripts are installed. These include lim, res, nios, sbatchd, mbatchd, and mbschd. If you use elim, eauth, eexec, esub, etc, they are also installed in this directory.
Load more

Recommended publications
  • Bash Shell Scripts
    Bash Shell Scripts Writing Bash shell scripts Bash shell scripts are text files Text files most efficiently built with programming editors (emacs or vi) File must be executable and in search path chmod 700 my_script PATH environment variable may not include .! An example shell script: #!/bin/bash #My first script echo "Hello World!" Bash Shell Scripts Writing Bash shell scripts Compile a Verilog file with vlog #!/bin/bash if [ ! d work ] ; then echo work does not exist, making it vlib work fi if [ ! s adder.v ] ; then vlog adder.v fi work directory must exist before compilation Get scripts via wget, eg: wget http://web.engr.oregonstate.edu/~traylor/ece474/script --- Bash Shell Scripts Writing Bash shell scripts File attribute checking #!/bin/bash if [ ! s junk_dir ] ; then mkdir junk_dir fi Spaces around brackets are needed! File attribute checking d exists and is a directory e, a file exists f exists and is a regular file s file exists and is not empty --- Bash Shell Scripts Writing Bash shell scripts Compile Verilog then run a simultion #!/bin/bash if [ ! -d "work" ] ; then vlib work fi if [ -s "adder.v" ] ; then vlog adder.v #runs simulation with a do file and no GUI vsim adder -do do.do quiet c else echo verilog file missing fi --- Bash Shell Scripts Writing Bash shell scripts vsim command and arguments vsim entity_name do dofile.do quiet -c -quiet (do not report loading file messages) -c (console mode, no GUI) -do (run vsim from a TCL do file) +nowarnTFMPC (don’t warn about mismatched ports, scary) +nowarnTSCALE (don’t warn about timing mismatches) Try vsim help for command line arguements --- Bash Shell Scripts Writing Bash Shell Scripts (TCL Script) In another text file, we create a TCL script with commands for the simulator.
    [Show full text]
  • Tcl/Tk for Xspecta Michael Flynn Tcl: Tcl (Ie Tool Command Language)
    Tcl/Tk for XSPECTa Michael Flynn Tcl: Tcl (i.e. Tool Command Language) is an open source scripting language similar to other modern script languages such as Perl or Python. It is substantially more powerful than UNIX/LINUX/POSIX shell script languages such as the Bourne Shell (sh), the C Shell (csh), or the Korn Shell (https://en.wikipedia.org/wiki/Shell_script). Tcl and its associated graphical user interface toolkit, Tk, were developed by John Ousterhout of the University of California. Ousterhout's group subsequently continued development of Tcl/Tk while at Sun Microsystems and later at Scriptics. Continued development is now done by an open source project team. The language has been popular for developing graphic applications and is available as public domain software for almost all computer systems (Linux, Windows and MacOS). Installation: Tcl/Tk software can be found at: http://www.activestate.com/activeTcl Binary Windows installers are available from this site for both 32 and 64 bit systems as a Free Community Edition. The lab modules were last validated with Version 8.6.4.1 but more recent versions should not be problematic. Unless Tcl has already been installed on the system being used, download and install the software from ActiveState. The installer should be run with administrative privileges. On Windows7, you should right click and 'run as administrator'. Installing with elevated privilege will allow the registry changes that map Tcl extensions and will configure the un-installer database, making later removal of ActiveTcl easier. The ActiveState default installation directory is C:/Tcl. During the installation, the installer will ask if you want this changed.
    [Show full text]
  • Shell Script Getopts Example
    Shell Script Getopts Example Gail is constrainedly cryoscopic after delegable Hilbert sag his parcloses illuminatingly. Gonzales often tootle irresistibly when tripersonal Giordano discomposed dissonantly and buffer her Barbarossa. Robert misdraws rompishly. Find that getopts script example we use later will contain whitespace separation with command Instantly share code, notes, and snippets. OPTARG is set to the period character found. They cease in many cases unneeded and brief fact that cartoon always press them its just like matter of personal coding style. File or directory or found. Operator precedence is used when there within five is more arguments. Typically, shell scripts use getopts to parse arguments passed to them. There did many ways to against your remedy environment. Nothing gets printed when no command line options are provided. The return status is zero unless an outcome is encountered while determining the name avid the he directory within an invalid option is supplied. The exit code will be success failure. Log in charge use details from one require these accounts. How does log lumber and cpu usage by an application? Now consider running it bore an unsupported option. No need only pass the positional parameters through to borrow external program. How can I check took a directory exists in a candy shell script? What extent its purpose? When optional, the fashion can buckle on led off additional functionality, as ugly a boolean option. In those cases, it contains a pointer to that parameter. How environment check ride a variable is set to Bash? Connect and deploy knowledge write a single location that is structured and fatigue to search.
    [Show full text]
  • Lecture 17 the Shell and Shell Scripting Simple Shell Scripts
    Lecture 17 The Shell and Shell Scripting In this lecture • The UNIX shell • Simple Shell Scripts • Shell variables • File System commands, IO commands, IO redirection • Command Line Arguments • Evaluating Expr in Shell • Predicates, operators for testing strings, ints and files • If-then-else in Shell • The for, while and do loop in Shell • Writing Shell scripts • Exercises In this course, we need to be familiar with the "UNIX shell". We use it, whether bash, csh, tcsh, zsh, or other variants, to start and stop processes, control the terminal, and to otherwise interact with the system. Many of you have heard of, or made use of "shell scripting", that is the process of providing instructions to shell in a simple, interpreted programming language . To see what shell we are working on, first SSH into unix.andrew.cmu.edu and type echo $SHELL ---- to see the working shell in SSH We will be writing our shell scripts for this particular shell (csh). The shell scripting language does not fit the classic definition of a useful language. It does not have many of the features such as portability, facilities for resource intensive tasks such as recursion or hashing or sorting. It does not have data structures like arrays and hash tables. It does not have facilities for direct access to hardware or good security features. But in many other ways the language of the shell is very powerful -- it has functions, conditionals, loops. It does not support strong data typing -- it is completely untyped (everything is a string). But, the real power of shell program doesn't come from the language itself, but from the diverse library that it can call upon -- any program.
    [Show full text]
  • Introduction to Shell Programming Using Bash Part I
    Introduction to shell programming using bash Part I Deniz Savas and Michael Griffiths 2005-2011 Corporate Information and Computing Services The University of Sheffield Email [email protected] [email protected] Presentation Outline • Introduction • Why use shell programs • Basics of shell programming • Using variables and parameters • User Input during shell script execution • Arithmetical operations on shell variables • Aliases • Debugging shell scripts • References Introduction • What is ‘shell’ ? • Why write shell programs? • Types of shell What is ‘shell’ ? • Provides an Interface to the UNIX Operating System • It is a command interpreter – Built on top of the kernel – Enables users to run services provided by the UNIX OS • In its simplest form a series of commands in a file is a shell program that saves having to retype commands to perform common tasks. • Shell provides a secure interface between the user and the ‘kernel’ of the operating system. Why write shell programs? • Run tasks customised for different systems. Variety of environment variables such as the operating system version and type can be detected within a script and necessary action taken to enable correct operation of a program. • Create the primary user interface for a variety of programming tasks. For example- to start up a package with a selection of options. • Write programs for controlling the routinely performed jobs run on a system. For example- to take backups when the system is idle. • Write job scripts for submission to a job-scheduler such as the sun- grid-engine. For example- to run your own programs in batch mode. Types of Unix shells • sh Bourne Shell (Original Shell) (Steven Bourne of AT&T) • csh C-Shell (C-like Syntax)(Bill Joy of Univ.
    [Show full text]
  • Simple Shell Scripting for Scientists
    Simple Shell Scripting for Scientists Day Three Julian King Bruce Beckles University of Cambridge Computing Service 1 Introduction • Who: ! Julian King, Unix Support, UCS ! Bruce Beckles, e-Science Specialist, UCS • What: ! Simple Shell Scripting for Scientists course, Day Three ! Part of the Scientific Computing series of courses • Contact (questions, etc): ! [email protected] • Health & Safety, etc: ! Fire exits • Please switch off mobile phones! [email protected] Simple Shell Scripting for Scientists: Day Three 2 As this course is part of the Scientific Computing series of courses run by the Computing Service, all the examples that we use will be more relevant to scientific computing than to system administration, etc. This does not mean that people who wish to learn shell scripting for system administration and other such tasks will get nothing from this course, as the techniques and underlying knowledge taught are applicable to shell scripts written for almost any purpose. However, such individuals should be aware that this course was not designed with them in mind. 2 What we don’t cover • Different types of shell: ! We are using the Bourne-Again SHell (bash). • Differences between versions of bash • Very advanced shell scripting – try one of these courses instead: ! “Python: Introduction for Absolute Beginners” ! “Python: Introduction for Programmers” [email protected] Simple Shell Scripting for Scientists: Day Three 3 bash is probably the most common shell on modern Unix/Linux systems – in fact, on most modern Linux distributions it will be the default shell (the shell users get if they don’t specify a different one).
    [Show full text]
  • QEMU Version 4.2.0 User Documentation I
    QEMU version 4.2.0 User Documentation i Table of Contents 1 Introduction ::::::::::::::::::::::::::::::::::::: 1 1.1 Features :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2 QEMU PC System emulator ::::::::::::::::::: 2 2.1 Introduction :::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2.2 Quick Start::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2.3 Invocation :::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.3.1 Standard options :::::::::::::::::::::::::::::::::::::::::: 3 2.3.2 Block device options :::::::::::::::::::::::::::::::::::::: 12 2.3.3 USB options:::::::::::::::::::::::::::::::::::::::::::::: 23 2.3.4 Display options ::::::::::::::::::::::::::::::::::::::::::: 23 2.3.5 i386 target only::::::::::::::::::::::::::::::::::::::::::: 30 2.3.6 Network options :::::::::::::::::::::::::::::::::::::::::: 31 2.3.7 Character device options:::::::::::::::::::::::::::::::::: 38 2.3.8 Bluetooth(R) options ::::::::::::::::::::::::::::::::::::: 42 2.3.9 TPM device options :::::::::::::::::::::::::::::::::::::: 43 2.3.10 Linux/Multiboot boot specific ::::::::::::::::::::::::::: 44 2.3.11 Debug/Expert options ::::::::::::::::::::::::::::::::::: 45 2.3.12 Generic object creation :::::::::::::::::::::::::::::::::: 54 2.3.13 Device URL Syntax ::::::::::::::::::::::::::::::::::::: 66 2.4 Keys in the graphical frontends :::::::::::::::::::::::::::::::: 69 2.5 Keys in the character backend multiplexer ::::::::::::::::::::: 69 2.6 QEMU Monitor ::::::::::::::::::::::::::::::::::::::::::::::: 70 2.6.1 Commands :::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Natural Shell: an Assistant for End-User Scripting
    International Journal of People-Oriented Programming Volume 5 • Issue 1 • January-June 2016 Natural Shell: An Assistant for End-User Scripting Xiao Liu, College of Information Sciences and Technology, Pennsylvania State University, University Park, PA, USA Yufei Jiang, College of Information Sciences and Technology, Pennsylvania State University, University Park, PA, USA Lawrence Wu, College of Information Sciences and Technology, Pennsylvania State University, University Park, PA, USA Dinghao Wu, College of Information Sciences and Technology, Pennsylvania State University, University Park, PA, USA ABSTRACT Scripting is a widely-used way to automate the execution of tasks. Despite the popularity of scripting, it remains difficult to use for both beginners and experts: because of the cryptic commands for the first group, and incompatible syntaxes across different systems, for the latter group. The authors introduce Natural Shell, an assistant for enabling end-users to generate commands and scripts for various purposes. Natural Shell automatically synthesizes scripts for different shell systems based on natural language descriptions. By interacting with Natural Shell, new users can learn the basics of scripting languages without the obstacles from the incomprehensible syntaxes. On the other hand, the authors’ tool frees more advanced users from manuals when they switch shell systems. The authors have developed a prototype system and demonstrate its effectiveness with a benchmark of 50 examples of popular shell commands collected from online forums. In addition, the authors analyzed the usage of Natural Shell in a lab study that involves 10 participants with different scripting skill levels. Natural Shell effectively assists the users to generate commands in assigned syntaxes and greatly streamlines their learning and using experience.
    [Show full text]
  • BASH Programming − Introduction HOW−TO BASH Programming − Introduction HOW−TO
    BASH Programming − Introduction HOW−TO BASH Programming − Introduction HOW−TO Table of Contents BASH Programming − Introduction HOW−TO.............................................................................................1 by Mike G mikkey at dynamo.com.ar.....................................................................................................1 1.Introduction...........................................................................................................................................1 2.Very simple Scripts...............................................................................................................................1 3.All about redirection.............................................................................................................................1 4.Pipes......................................................................................................................................................1 5.Variables...............................................................................................................................................2 6.Conditionals..........................................................................................................................................2 7.Loops for, while and until.....................................................................................................................2 8.Functions...............................................................................................................................................2
    [Show full text]
  • A Shell Script for Preparing Your Trials with a Standard Set-Up
    PhUSE US Connect 2019 Paper CT04 Quick Start Your Trials – A Shell Script for Preparing Your Trials with a Standard Set-up Edita Karosiene, Novo Nordisk A/S, Søborg, Denmark Johan Ejstrud, Novo Nordisk A/S, Aalborg, Denmark ABSTRACT In this paper we present a shell script which can set-up your trial in a few seconds. The script is using a template directory where the files needed to start a trial are placed. It can automatically find all the files in the template directory and copy them to the corresponding trial directory. If the trial ID is used anywhere in the file or directory name or within the file content, it will be replaced with an actual trial ID. In addition to this, the script automatically recognizes the updates made in the template directory so files can be easily moved, added or removed within the template with no need to update the script. The shell script can run on UNIX® or Linux® servers and can easily be adjusted for any other tasks as well. INTRODUCTION It is often the case that clinical trials or projects will have a similar technical set-up within the same company. That includes having some dedicated locations where all trial directories are placed and having a naming convention to name them. Moreover, there should be an overlap between directory structure and files that are used for many trials. This suggests an idea to have a trial template directory ready which is utilized as an example for every new trial. Having such template is already a very good idea, however it is very important to use it efficiently.
    [Show full text]
  • A Quickie Intro to UNIX, Linux, Macosx the Filesystem + Some Tools
    Introduction to UNIX Notes . Alistair Blachford A Quickie Intro to UNIX, Linux, MacOSX The Filesystem + some tools For Snooping Around 1) pwd • print the working directory 2) ls • list names of the files and subdirectories in the current directory ? ls -F list directory contents, with terminating marks to indicate subdirectories and executable files. ? ls -a list all files, even those begining with a ‘.’ ? ls -l list files in ‘long’ form giving a lot of information about each one 3) cd dirname • change the current working directory to dirname ? cd data.d change whatever the current working directory is to the directory data.d. This example assumes data.d is a subdirectory (child) of the current directory. ? cd .. change working directory to the one immediately above (parent). ? cd cd with no arguments means go to the default place — your home directory 4) who • print the list of users currently logged onto this computer 5) date • print the date and time 6) cat filename... • “copy all text” of filename(s) to the screen. When more than one filename is given, the files are concatenated end-to-end. 7) more filename • will “cat” a file to the screen, one screenfull at a time. Hit <return> to advance by only one line, <space bar> to advance by a screenfull, and <q> to quit. 8) file filename • this will make a good guess at what is contained in the file filename. Some possible responses are: binary data, ASCII text, C program text, shell commands text. 1 Introduction to UNIX Notes . Alistair Blachford For Shuffling Files 9) rm file.
    [Show full text]
  • How to Configure the NFX250
    How to Configure the NFX250 Published 2021-07-12 ii Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. How to Configure the NFX250 Copyright © 2021 Juniper Networks, Inc. All rights reserved. The information in this document is current as of the date on the title page. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036. END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement ("EULA") posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA. iii Table of Contents About This Guide | ix 1 Overview NFX250 Overview | 2 JDM
    [Show full text]