DOCSLIB.ORG

Scripting Perforce Introduction

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Scripting Perforce Introduction Perforce Training, 2010.1 Scripting Perforce Introduction • Introductions • Class Schedule • About the Exercises 1 Perforce Training, 2010.1 Intended course audience • Experienced Perforce users who need to write scripts • Configuration management, build, and release engineers, and others Prerequisite experience • PfPerforce user and ddiitt administrator • Writing scripts using Perl 2 Perforce Training, 2010.1 Objectives • DlDevelop scr ittfipts to perform common tktasks • Follow best practices Uses of scripts • Web browser interface to Perforce • Plug-in for an IDE • Back-up and recovery routines • Wrappers for Perforce commands • Customized d iff a nd me rge too l s • Conversion from other SCM tools 3 Perforce Training, 2010.1 Script examples in this course • Automating processes • Generating reports • Sending email • Process support • Auditing metadata Course Contents • Preliminary Decisions • Perforce Commands for Scripting • Command Line Program (p4) • Application Program Interface (API) • Daemons • TiTriggers • Wrappers and Administrative Scripts 4 Perforce Training, 2010.1 Preliminary Decisions • Setting Environment Variables • User Authentication • Client Program Interface Preliminary Decisions Setting Environment Variables 5 Perforce Training, 2010.1 Use global options • Set environment variables in script p4 –p serverport –u username info • Advantage: Overrides all other settings • Disadvantage: Edit each script to change Use configuration files • Set P4CONFIG to a file name p4 set P4CONFIG=config.txt • Place config.txt files in script folders • List environment variables in config.txt P4PORT=lemon:1909 P4CLIENT=script_user_reporter P4USER=script_user 6 Perforce Training, 2010.1 P4CONFIG example Environment Variable: P4CONFIG=config.txt C:\scripts P4PORT=krypton:1666 P4CLIENT=scriptuser-prod config.txt P4USER=scriptuser \Krypton P4PORT=xenon:1666 P4CLIENT=report-writer config.txt P4USER=reporter \Xenon Using P4CONFIG • Advantages • Configures many scripts • Active in specific directories • Disadvantage • If P4CONFIG unset, script environment may change 7 Perforce Training, 2010.1 Use environment variables • Set environment variables (Windows) p4 set P4PORT=p4demo.com:1666 • List environment variables p4 set P4CLIENT=b ru no o_w s (set) P4PORT=p4demo.com:1666 (set) P4USER=bruno (set) Using environment variables • Advantaggye: Easy to set • Disadvantages • May be accidentally changed • Depends upon shell being used 8 Perforce Training, 2010.1 Configuration order of precedence • Command-line flags • P4CONFIG files • Environment variable settings • Registry variable settings (on Windows) • Default value for environment variables Preliminary Decisions User Authentication 9 Perforce Training, 2010.1 Use login • Works for all server security levels • Usage: p4 login Enter password: UitldiUser script_user logged in. Use a group to extend session p4 group scriptsonly Group: scriptsonly MaxResults: 100000 Maxscanrows: 500000 MaxLockTime: 30000 Timeout: unlimited Subgroups: Owners: bruno Users: script_user 10 Perforce Training, 2010.1 Use a password • Security levels 0-2 p4 -P Script_pass users • Security level 3 p4 login -p Enter password: 9CC3EACDEFCC8C7020C134D6D333F46F p4 -P 9CC3EACDEFCC8C7020C134D6D333F46F users Preliminary Decisions Client Program Interface 11 Perforce Training, 2010.1 Comparing client program interfaces Command Line Program Apppplication Prog ram Interface p4 Perforce C/C++ API One connection per User controls connection command Returns lines of text Tagged data available Some language support Language derivatives available Java-native API (P4Java) Objective-C API (P4ObjC) Tagging output: Command line and API • Command line returns lines of text • Format output by using -ztag p4 -ztag clients ... client bruno_ws ... Update 1104271684 ... Access 1104340062 ... etc. • Perforce API supports tagged data output 12 Perforce Training, 2010.1 Command line program: bypass an editor • Redirect to standard output p4 change -o • Read from standard input p4 submit -i Command line program: Using Python • Create Python marshalled dictionary object p4 -G job -o 13 Perforce Training, 2010.1 Sample Python Script and p4 -G Output #!/usr/local/bin/python #Example script named readmarshal.py import marshal, sys true = 1 try: while true: vars = marshal.load(sys.stdin) print vars except EOFError: '' #note that these are two single-quotes p4 -G user -o raj |dhl| readmarshal.py {'Email': '[email protected]', 'Update': '2005/12/06 11:16:30', 'Reviews1': '//depot/dev/main/...', 'Reviews0': '//depot/www/...', 'FullName': 'Raj Bai', 'User': 'raj', 'code': 'stat', 'Access': '2006/07/06 15:16:30'} Command line program: Using Ruby • Create Ruby marshalled dictionary object p4 -R job –o 14 Perforce Training, 2010.1 Sample Ruby script and p4 -R output # Example script named readruby.rb f = IO.popen("p4 -R user -o " + ARGV[0]) user_info = Marshal.load(f) p user_info readruby.rb bruno {"code"=>"stat", "User"=>"bruno", "Email"=>"[email protected]", "FullName"=>"Bruno Batswan"} Perforce’s derived APIs • P4Per l • P4Python • P4Ruby 15 Perforce Training, 2010.1 Scripting environment for the exercises • Use P4CONFIG to Set Environment Variables • User Authentication p4 login • Client Program Interface • p4 and API (using P4Perl) examples Scripting Perforce Exercise Setting the Perforce Environment 16 Perforce Training, 2010.1 Scripting Perforce Perforce Commands for Scripting Perforce Commands for Scripting • General • Review Daemons • Data Mining 17 Perforce Training, 2010.1 Perforce Commands General Capture errors, warnings and messages p4 -s opened -c default error: File(s) not opened on this client. exit: 0 18 Perforce Training, 2010.1 Submit without invoking an editor p4 submit -d "Fixed results of sim scans." Submitting change 1825. Locking 2 files ... edit //Sim/Prod/MAIN/src/sim.c#36 edit //Sim/Prod/MAIN/src/scan.c#2 Change 1825 submitted. Script efficiently • Limit number of lines of data returned • Narrow scope of Perforce commands • Refer to known workspace spec • Access small ggproups of dep ot files 19 Perforce Training, 2010.1 List a single changelist UiUsing a c lient wor kspace name p4 changes -m1 –s submitted –c raj-spruce Change 421 on 2001/01/07 by raj@raj-spruce 'Update sim to work reasonably on' List several changelists Using a depot path p4 changes –m10 //depot/www/... Change 1769 on 2006/12/11 by quinn@quinn-azalea 'Copy jamgraph example to web' Change 1763 on 2006/11/23 by hera@hera-amphora 'Jamgraph 1.0 is live.' ...etc. 20 Perforce Training, 2010.1 Perforce Commands Review Daemons Use a counter • Set personal counter p4 counter notifyd 746 Counter notifyd set. • Poll a counter p4 counter notifyd 746 21 Perforce Training, 2010.1 List all counter values p4 counters change = 750 job = 4 journal = 15 notifyd = 746 ... etc. Review daemon tools • View changelists past counter value p4 review -t notifydy Change 747 bruno [email protected](Bruno Batswan) Change 749 brad [email protected](Brad Manners) Change 750 sam [email protected](Sam Maxwell) • View subscribers for email notification p4 reviews -c 747 bruno <[email protected]> (Bruno Batswan) laura <[email protected]> (Laura Germain) 22 Perforce Training, 2010.1 Change your user profile p4 user User: earl Email: [email protected] Update: 2007/08/09 13:45:59 Access: 2008/03/07 16:45:05 FullName: Earl Ashby Reviews: Add “Reviews:” field if //Sim/Prod/MAIN/... running review daemon //depot/www/... List recently edited/created jobs p4 jobs -e "date>=2007/06/21" job002127 on 2007/11/19 by earl *open* ‘Fix parse error’ job002097 on 2007/10/21 by raj *closed* ‘Exit off’ job001931 on 2007/10/16 by gail *punted* ‘Web style’ job001762 on 2007/07/08 by raj *closed* ‘Scan func’ 23 Perforce Training, 2010.1 List fixed jobs p4 fixes //Sim/Prod/MAIN/src/... job000001 fixed by change 55 on 1999/01/19 by earl@earl-dev job000002 fixed by change 114 on 1999/02/28 by earl@earl-dev job000003 fixed by change 114 on 1999/02/28 by earl@earl-dev job000004 fixed by change 148 on 1999/07/19 by earl@earl-dev job000004 fixed by change 132 on 1999/04/30 by earl@earl-dev ... etc. Perforce Commands Data Mining 24 Perforce Training, 2010.1 Report depot data • List directories p4 dirs //depot/* //depot/Jam //depot/Jamgraph ...etc. • List files p4 files //depot/Jam/MAIN/src/... //depot/Jam/MAIN/src/Build.com#9 - edit change 839 //depot/Jam/MAIN/src/Build.mpw#3 - edit change 839 //depot/Jam/MAIN/src/command.c#12 - edit change 839 ...etc. Gather file data as tagged output p4 fstat execcmd.h ... depotFile //depot/Jam/MAIN/src/execcmd. h ... clientFile c:\raj\Jam\MAIN\src\execcmd.h ... isMapped ... headAction edit ... headType text ... headTime 1106848927 ... headRev 2 ... headChange 30 ... headModTime 1106847314 ... haveRev 2 25 Perforce Training, 2010.1 Report on a single file p4 annotate -ac jam. c //depot/Jam/MAIN/src/jam.c#37 - edit change 93 (text) 1-93: /* 1-1: * Copyright 1993 Christopher Seiwald. 30-93: * Copyright 1993, 1995 Christopher Seiwald. ... etc. Search for patterns in files p4 grep -a -n -F -e "/* debug */" jam.c //depot/Jam/MAIN/src/jam.c#14:114: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#13:114: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#12:114: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#11:106: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#10:106: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#9:96: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#8:96: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#6:93: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#5:93: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#4:93: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#3:93: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#2:91: 1, /* debug */ //depot/Jam/MAIN/src/jam.c#1:86: 1, /* debug */ 26 Perforce Training, 2010.1 Report Perforce metadata • Lis t a ll c lien t wor kspace specs p4 clients • List client workspace specs by owner p4 clients –u bruno Use -n flag to report status p4 integrate -n -b SimMAINtoFLAT //Sim/Prod/FLAT/src/scan.c#3 sync/integrate from //Sim/Prod/MAIN/src/scan.c#12 //Sim/Prod/FLAT/src/scan.h#2 sync/integrate from //Sim/Prod/MAIN/src/scan.h#14 ...etc.
Load more

Recommended publications
  • Shell Scripting with Bash
    Introduction to Shell Scripting with Bash Charles Jahnke Research Computing Services Information Services & Technology Topics for Today ● Introductions ● Basic Terminology ● How to get help ● Command-line vs. Scripting ● Variables ● Handling Arguments ● Standard I/O, Pipes, and Redirection ● Control Structures (loops and If statements) ● SCC Job Submission Example Research Computing Services Research Computing Services (RCS) A group within Information Services & Technology at Boston University provides computing, storage, and visualization resources and services to support research that has specialized or highly intensive computation, storage, bandwidth, or graphics requirements. Three Primary Services: ● Research Computation ● Research Visualization ● Research Consulting and Training Breadth of Research on the Shared Computing Cluster (SCC) Me ● Research Facilitator and Administrator ● Background in biomedical engineering, bioinformatics, and IT systems ● Offices on both CRC and BUMC ○ Most of our staff on the Charles River Campus, some dedicated to BUMC ● Contact: [email protected] You ● Who has experience programming? ● Using Linux? ● Using the Shared Computing Cluster (SCC)? Basic Terminology The Command-line The line on which commands are typed and passed to the shell. Username Hostname Current Directory [username@scc1 ~]$ Prompt Command Line (input) The Shell ● The interface between the user and the operating system ● Program that interprets and executes input ● Provides: ○ Built-in commands ○ Programming control structures ○ Environment
    [Show full text]
  • Powerview Command Reference
    PowerView Command Reference TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... PowerView User Interface ............................................................................................................ PowerView Command Reference .............................................................................................1 History ...................................................................................................................................... 12 ABORT ...................................................................................................................................... 13 ABORT Abort driver program 13 AREA ........................................................................................................................................ 14 AREA Message windows 14 AREA.CLEAR Clear area 15 AREA.CLOSE Close output file 15 AREA.Create Create or modify message area 16 AREA.Delete Delete message area 17 AREA.List Display a detailed list off all message areas 18 AREA.OPEN Open output file 20 AREA.PIPE Redirect area to stdout 21 AREA.RESet Reset areas 21 AREA.SAVE Save AREA window contents to file 21 AREA.Select Select area 22 AREA.STDERR Redirect area to stderr 23 AREA.STDOUT Redirect area to stdout 23 AREA.view Display message area in AREA window 24 AutoSTOre ..............................................................................................................................
    [Show full text]
  • An Empirical Comparison of Widely Adopted Hash Functions in Digital Forensics: Does the Programming Language and Operating System Make a Difference?
    2015 Annual ADFSL Conference on Digital Forensics, Security and Law Proceedings May 19th, 11:45 AM An Empirical Comparison of Widely Adopted Hash Functions in Digital Forensics: Does the Programming Language and Operating System Make a Difference? Satyendra Gurjar Cyber Forensics Research and Education Group (UNHcFREG), Tagliatela College of Engineering, ECECS Department, University of New Haven, [email protected] Ibrahim Baggili Cyber Forensics Research and Education Group (UNHcFREG), Tagliatela College of Engineering, ECECS Department, University of New Haven Frank Breitinger CyberFollow F thisorensics and additional Research worksand Education at: https:/ Gr/commons.eroup (UNHcFREG),au.edu/adfsl Tagliatela College of Engineering, ECECS Depar Partment,t of the Univ Aviationersity ofSaf Newety and Hav Securityen Commons, Computer Law Commons, Defense and Security AliceStudies Fischer Commons , Forensic Science and Technology Commons, Information Security Commons, CyberNational For Securityensics Resear Law Commonsch and Education, OS and GrNetworksoup (UNHcFREG), Commons T, Otheragliatela Computer College Sciences of Engineering, Commons ECECS, and theDepar Socialtment, Contr Univol,ersity Law , ofCrime, New andHav enDe,viance AFischer@newha Commons ven.edu Scholarly Commons Citation Gurjar, Satyendra; Baggili, Ibrahim; Breitinger, Frank; and Fischer, Alice, "An Empirical Comparison of Widely Adopted Hash Functions in Digital Forensics: Does the Programming Language and Operating System Make a Difference?" (2015). Annual ADFSL Conference on Digital Forensics, Security and Law. 6. https://commons.erau.edu/adfsl/2015/tuesday/6 This Peer Reviewed Paper is brought to you for free and open access by the Conferences at Scholarly Commons. It has been accepted for inclusion in Annual ADFSL Conference on Digital Forensics, Security and Law by an (c)ADFSL authorized administrator of Scholarly Commons.
    [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]
  • CMSC 426/626 - Computer Security Fall 2014
    Authentication and Passwords CMSC 426/626 - Computer Security Fall 2014 Outline • Types of authentication • Vulnerabilities of password authentication • Linux password authentication • Windows Password authentication • Cracking techniques Goals of Authentication • Identification - provide a claimed identity to the system. • Verification - establish validity of the provided identity. We’re not talking about message authentication, e.g. the use of digital signatures. Means of Authentication • Something you know, e.g. password • Something you have, e.g. USB dongle or Common Access Card (CAC) • Something you are, e.g. fingerprint • Something you do, e.g. hand writing Password-Based Authentication • User provides identity and password; system verifies that the password is correct for the given identity. • Identity determines access and privileges. • Identity can be used for Discretionary Access Control, e.g. to give another user access to a file. Password Hashing Password • System stores hash of the user password, not the plain text password. Hash Algorithm • Commonly used technique, e.g. UNIX password hashing. Password Hash Password Vulnerabilities Assume the authentication system stores hashed passwords. There are eight attack strategies. • Off-line Dictionary Attack - get hold of the password file, test a collection (dictionary) of possible passwords. ‣ Most systems protect the password file, but attackers sometimes get hold of one. • Specific Account Attack - given a specific user account, try popular passwords. ‣ Most systems use lockout mechanisms to make these attacks difficult. • Popular Password Attack - given a popular password, try it on multiple accounts. ‣ Harder to defend against - have to look for patterns in failed access attempts. • Targeted Password Guessing - use what you know about a user to intelligently guess their password.
    [Show full text]
  • Jellyfish Count -M 21 -S 100M -T 10 -C Reads.Fasta
    Jellysh 2 User Guide December 13, 2013 Contents 1 Getting started 2 1.1 Counting all k-mers . .2 1.1.1 Counting k-mers in sequencing reads . .3 1.1.2 Counting k-mers in a genome . .3 1.2 Counting high-frequency k-mers . .3 1.2.1 One pass method . .3 1.2.2 Two pass method . .4 2 FAQ 5 2.1 How to read compressed les (or other format)?newmacroname . .5 2.2 How to read multiple les at once? . .5 2.3 How to reduce the output size? . .6 3 Subcommands 7 3.1 histo .............................................7 3.2 dump .............................................7 3.3 query .............................................7 3.4 info ..............................................8 3.5 merge ............................................8 3.6 cite . .8 1 Chapter 1 Getting started 1.1 Counting all k-mers The basic command to count all k-mers is as follows: jellyfish count -m 21 -s 100M -t 10 -C reads.fasta This will count canonical (-C) 21-mers (-m 21), using a hash with 100 million elements (-s 100 M) and 10 threads (-t 10) in the sequences in the le reads.fasta. The output is written in the le 'mer_counts.jf' by default (change with -o switch). To compute the histogram of the k-mer occurrences, use the histo subcommand (see section 3.1): jellyfish histo mer_counts.jf To query the counts of a particular k-mer, use the query subcommand (see section 3.3): jellyfish query mer_counts.jf AACGTTG To output all the counts for all the k-mers in the le, use the dump subcommand (see section 3.2): jellyfish dump mer_counts.jf > mer_counts_dumps.fa To get some information on how, when and where this jellysh le was generated, use the info subcommand (see section 3.4): jellyfish info mer_counts.jf For more detail information, see the relevant sections in this document.
    [Show full text]
  • Husky: Towards a More Efficient and Expressive Distributed Computing Framework
    Husky: Towards a More Efficient and Expressive Distributed Computing Framework Fan Yang Jinfeng Li James Cheng Department of Computer Science and Engineering The Chinese University of Hong Kong ffyang,jfli,[email protected] ABSTRACT tends Spark, and Gelly [3] extends Flink, to expose to programmers Finding efficient, expressive and yet intuitive programming models fine-grained control over the access patterns on vertices and their for data-parallel computing system is an important and open prob- communication patterns. lem. Systems like Hadoop and Spark have been widely adopted Over-simplified functional or declarative programming interfaces for massive data processing, as coarse-grained primitives like map with only coarse-grained primitives also limit the flexibility in de- and reduce are succinct and easy to master. However, sometimes signing efficient distributed algorithms. For instance, there is re- over-simplified API hinders programmers from more fine-grained cent interest in machine learning algorithms that compute by fre- control and designing more efficient algorithms. Developers may quently and asynchronously accessing and mutating global states have to resort to sophisticated domain-specific languages (DSLs), (e.g., some entries in a large global key-value table) in a fine-grained or even low-level layers like MPI, but this raises development cost— manner [14, 19, 24, 30]. It is not clear how to program such algo- learning many mutually exclusive systems prolongs the develop- rithms using only synchronous and coarse-grained operators (e.g., ment schedule, and the use of low-level tools may result in bug- map, reduce, and join), and even with immutable data abstraction prone programming.
    [Show full text]
  • Daniel Lyons [email protected] Why?
    How to Hurt Your Friends with (loop) Daniel Lyons [email protected] Why? Fast Powerful Widely-used Like format you can probably do more with it than you realize. Even though you hate it, you may have to read it in someone else’s code. On my machine, 578 of 1068 library files contain at least one loop form (54.12%). It’s fast as hell. loop as List Comprehension Python: [ f(x) for x in L if p(x) ] Haskell: [ f(x) | x <- L, p(x) ] Erlang: [ f(X) || X <- L, p(X) ]. Loop: (loop for x in L when (p x) collect (f x)) Things You Can Do With loop Variable initialization and stepping Value accumulation Conditional and unconditional execution Pre- and post-loop operations Termination whenever and however you like This is taken from the list of kinds of loop clauses from CLtL Ch. 26 - variable initialization and stepping - value accumulation - termination conditions - unconditional execution - conditional execution - miscellaneous operations Initialization for/as with repeat for and as mean the same thing with is a single ‘let’ statement repeat runs the loop a specified number of times for Is Really Complicated for var from expr to expr for var in expr for var on expr Of course from can also be downfrom or upfrom, and to can also be downto, upto, below or above for var in expr: Loops over every item in the list Optionally by some stepping function for var on expr loops over the cdrs of a list, giving you each successive sublist Loops over each sublist of the list, e.g.
    [Show full text]
  • Linux Command Line: Aliases, Prompts and Scripting
    Linux Command Line: Aliases, Prompts and Scri... 1 Linux Command Line: Aliases, Prompts and Scripting By Steven Gordon on Wed, 23/07/2014 - 7:46am Here are a few notes on using the Bash shell that I have used as a demo to students. It covers man pages, aliases, shell prompts, paths and basics of shell scripting. For details, see the many free manuals of Bash shell scripting. 1. Man Pages Man pages are the reference manuals for commands. Reading the man pages is best when you know the command to use, but cannot remember the syntax or options. Simply type man cmd and then read the manual. E.g.: student@netlab01:~$ man ls If you don't know which command to use to perform some task, then there is a basic search feature called apropos which will do a keyword search through an index of man page names and short descriptions. You can run it using either the command apropos or using man -k. E.g.: student@netlab01:~$ man superuser No manual entry for superuser student@netlab01:~$ apropos superuser su (1) - change user ID or become superuser student@netlab01:~$ man -k "new user" newusers (8) - update and create new users in batch useradd (8) - create a new user or update default new user information Some common used commands are actually not standalone program, but commands built-in to the shell. For example, below demonstrates the creation of aliases using alias. But there is no man page for alias. Instead, alias is described as part of the bash shell man page.
    [Show full text]
  • The Xargs Package
    The xargs package Manuel Pégourié-Gonnard [email protected] v1.1 (2008/03/22) Contents 1 Introduction 1 2 Usage 1 3 Implementation 4 Important note for French users: a French version of the user documentation is included in the xargs-fr.pdf file. 1 Introduction A Defining commands with an optional argument is easy in LTEX2ε. There is, how- ever, two limitations: you can make only one argument optional and it must be the first one. The xargs package provide extended variants of \newcommand & friends, for which these limitations no longer hold: It is now easy to define commands with many (and freely placed) optional arguments, using a nice hkeyi=hvaluei syntax. For example, the following defines a command with two optional arguments. \newcommandx*\coord[3][1=1, 3=n]{(#2_{#1},\ldots,#2_{#3})} $\coord{x}$ (x1,...,xn) $\coord[0]{y}$ (y0,...,yn) $\coord{z}[m]$ (z1,...,zm) $\coord[0]{t}[m]$ (t0,...,tm) 2 Usage 2.1 Basics The xargs package defines an extended variant for every LATEX macro related to macro definition. xargs’s macro are named after their LATEX counterparts, just adding an x at end (see the list in the margin). Here is the complete list: \newcommandx \renewcommandx \newenvironmentx \renewenvironmentx \providecommandx \DeclareRobustCommandx \CheckCommandx 1 If you are not familiar with all of them, you can either just keep using the A commands you already know, or check Lamport’s book or the LTEX Companion (or any LATEX2ε manual) to learn the others. Since these commands all share the same syntax, I’ll always use \newcommandx in the following, but remember it works the same for all seven commands.
    [Show full text]
  • Table of Contents Local Transfers
    Table of Contents Local Transfers......................................................................................................1 Checking File Integrity.......................................................................................................1 Local File Transfer Commands...........................................................................................3 Shift Transfer Tool Overview..............................................................................................5 Local Transfers Checking File Integrity It is a good practice to confirm whether your files are complete and accurate before you transfer the files to or from NAS, and again after the transfer is complete. The easiest way to verify the integrity of file transfers is to use the NAS-developed Shift tool for the transfer, with the --verify option enabled. As part of the transfer, Shift will automatically checksum the data at both the source and destination to detect corruption. If corruption is detected, partial file transfers/checksums will be performed until the corruption is rectified. For example: pfe21% shiftc --verify $HOME/filename /nobackuppX/username lou% shiftc --verify /nobackuppX/username/filename $HOME your_localhost% sup shiftc --verify filename pfe: In addition to Shift, there are several algorithms and programs you can use to compute a checksum. If the results of the pre-transfer checksum match the results obtained after the transfer, you can be reasonably certain that the data in the transferred files is not corrupted. If
    [Show full text]
  • Unix-Like Access Permissions in Fully Decentralized File Systems
    Unix-like Access Permissions in Fully Decentralized File Systems Johanna Amann∗ Thomas Fuhrmann Technische Universitat¨ Munchen¨ Technische Universitat¨ Munchen¨ [email protected] [email protected] Current fully decentralized file systems just offer basic lic and a private part. World-readable files are stored access semantics. In most systems, there is no integrated in the public part of the group-directory in addition to access control. Every user who can access a file system the owner’s user-directory. Files that are only readable can read and sometimes even write all data. Only few by the group are stored in the private part of the group- systems offer better protection. However, they usually directory. Files that are only readable by the owning user involve algorithms that do not scale well, e. g. certifi- are only stored in the owner’s user-directory. The private cates that secure the file access rights. Often they require group directory is secured with a group encryption key. online third parties. To the best of our knowledge all sys- This encryption key is distributed to the group members tems also lack the standard Unix access permissions, that using the subset difference encryption scheme. When a users have become accustomed to. file-owner writes a file, the copy in her user-directory is In this poster, we show a decentralized, cryptograph- updated. When a group-member updates a file, the copy ically secure, scalable, and efficient way to introduce in the group-directory is updated. Both places have to be nearly the full spectrum of Unix file system access per- checked on access for the most recent version.
    [Show full text]