DOCSLIB.ORG

Command Reference Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Command Reference Guide Command Reference Guide SmartWare Release 2.00 Customer Deliverable Documentation Part Number 80-0125 English Revision 1.01, May 22, 2002 Legal Notice 3 LEGAL NOTICE SmartWare Command Reference Guide Copyright © 2002 Inalp Networks AG All rights reserved. No part of this publication may be reproduced without prior written permission from Inalp Networks AG. Limitations of Use Inalp Networks AG reserves the right to make changes in specifications and other information contained in this document without prior notice. The information provided is subject to change without notice. In no event shall Inalp Networks AG or its employees and associated companies be liable for any incidental, special, indirect or consequential damages whatsoever, including but not limited to lost profits, arising out of or related to this manual or the information contained within it, even if Inalp Networks AG has been advised of, known, or should have known, the possibility of such damages. Trademarks Inalp, the Inalp Logo, and SmartNode are registered trademarks of Inalp Networks AG. SmartWare and SmartView are trademarks of Inalp Networks AG. All other trademarks mentioned in this document are property of their respective owners. EU Declaration of Conformity The EU Directives covered by this Declaration 89/336/EEC Electromagnetic Compatibility Directive amended by 92/31/EEC & 93/68/EEC 72/23/EEC Low Voltage Equipment Directive amended by 93/68/EEC Note: During the transition period, products may not comply with the Low Voltage Directive. The Products covered by this Declaration The products covered by this declaration are the SmartNode 1000 and 2000 family series devices. The Basis on which Conformity is being Declared The products identified above comply with the requirements of the above EU directives by meeting the following standards: • Safety compliance: EN 60950 • EMC compliance: EN 55022, EN 55024 • ETSI TBR3 (BRI) • TBR4 (PRI) The CE mark was first applied in 2000. Inalp Networks AG Meriedweg 7 CH-3172 Niederwangen Command Reference Guide, Revision 1.01 4 Table of Contents TABLE OF CONTENTS Legal Notice.......................................................................................................................................................... 3 Table of Contents................................................................................................................................................ 4 About This Guide ............................................................................................................................................. 12 1 Command Line Interface ......................................................................................................................... 15 1.1 Introduction ........................................................................................................................................ 15 1.2 Modes and Mode Groups ................................................................................................................. 15 1.2.1 Modes........................................................................................................................................... 15 1.2.2 Mode Groups .............................................................................................................................. 15 1.2.3 System Prompt............................................................................................................................ 15 1.3 Navigating the CLI............................................................................................................................. 16 1.3.1 Initial Mode................................................................................................................................. 16 1.3.2 System Changes.......................................................................................................................... 16 1.3.3 Configuration.............................................................................................................................. 16 1.3.4 Changing Mode and Exit ..........................................................................................................16 1.4 Command Editing.............................................................................................................................. 19 1.4.1 Command Help .......................................................................................................................... 19 1.4.2 Command No Form................................................................................................................... 20 1.4.3 Command Completion..............................................................................................................20 1.4.4 Command History...................................................................................................................... 20 1.4.5 Command Editing Shortcuts .................................................................................................... 21 1.4.6 Command Confirmation ........................................................................................................... 21 1.5 Basic User Interface Commands....................................................................................................... 21 ?, help........................................................................................................................................................... 22 exit ................................................................................................................................................................ 24 2 Operator Execution Mode........................................................................................................................ 25 2.1 Command Overview ......................................................................................................................... 25 call ................................................................................................................................................................ 26 clear .............................................................................................................................................................. 29 debug call .................................................................................................................................................... 30 jobs ............................................................................................................................................................... 31 fg................................................................................................................................................................... 33 logout ........................................................................................................................................................... 35 ping .............................................................................................................................................................. 36 show call...................................................................................................................................................... 38 show clock................................................................................................................................................... 39 show dsp...................................................................................................................................................... 40 show framerelay......................................................................................................................................... 41 show history................................................................................................................................................ 42 show ip interface ........................................................................................................................................ 43 show ip route .............................................................................................................................................. 45 show log ...................................................................................................................................................... 47 show napt interface.................................................................................................................................... 49 show port ethernet ..................................................................................................................................... 51 show port isdn............................................................................................................................................ 52 show port serial .......................................................................................................................................... 53 show profile call-progress-tone................................................................................................................ 54 show profile tone-set.................................................................................................................................. 56 Command Reference Guide, Revision 1.01 Table of Contents 5 show profile voip ....................................................................................................................................... 58 show
Load more

Recommended publications
  • Commands to Control Device
    Commands to Control Device New OTA firmware upgrade command. To try it via over-the-air update, use these commands: > fwe > fwd B6FMA186 The board will reboot after the first command, this is normal. After the second command wait 1-3 minutes (seems like a long time). After it resets again, go back to BlueFruit and press "info" the software should be 3.0.186 The default wakeup interval is still 4 hours (14400 seconds). To configure a unit for a different wakeup interval: >wakt 600 (this would be 60*10 = 10 minutes) No beeps (Command to turn off the beeps) nvap 6 120000 14400000 15000 5000 0 223 1 3 Command to Restore Beeps nvap 6 120000 14400000 15000 5000 0 223 1 65535 Main Menu commands ---- SubMenus -------------------------- >i - I2C menu >l - Log menu >M - Modem menu ---- Device Control Cmds --------------- >D [n] - set debug level to [n] >info - Show device info >cota - CDMA OTA reprovision >svrm [name] - Set server main >nvmr - Non-volatile memory revert >t - show system uptime >rst - Hard reset ---- General Cmds ---------------------- >c [str] - Execute remote command manually >batq - Query battery state >slp - Go to sleep immediately >slpt [n] - Set sleep timeout to [n] seconds >wakt [n] - Set wake timeout to [n] hours >sus - Suspend immediately >sts - Show statistics and send to server >bt [n] - Bluetooth disable/enable: n=0/1 >dsms [n] - DebugSMS configure 0/1=disabled/enabled >wss [p] [s] - WiMM Server Send [p]ort, [s]tring >wsr - WiMM Server Recv ---- Pos/Log Cmds ---------------------- >pn - Position now >plc {i} {t} - Position log ctrl, [i]nterval, [t]ripId Stop Logging >pla {i} {t} - Position log auto, [i]nterval, [t]ripId >plb {n} - Position log batch [n] records >ple - Position log erase --- Alarm Cmds ------------------------ >alm [m] - Alarm mode: m=0/1/2: Off/On/FireNow ---- Firmware Cmds --------------------- >fwd [v] - Firmware Download (WIMM{v}.hex) >fwl {i} - Firmware Launch (i=0/1: ImgA/B) >fwe - Firmware Erase (ImgB) To change the alarm delay You must be running firmware 145 or later.
    [Show full text]
  • Administering Unidata on UNIX Platforms
    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
    [Show full text]
  • Cisco Telepresence Codec SX20 API Reference Guide
    Cisco TelePresence SX20 Codec API Reference Guide Software version TC6.1 April 2013 Application Programmer Interface (API) Reference Guide Cisco TelePresence SX20 Codec D14949.03 SX20 Codec API Reference Guide TC6.1, April 2013. 1 Copyright © 2013 Cisco Systems, Inc. All rights reserved. Cisco TelePresence SX20 Codec API Reference Guide What’s in this guide? Table of Contents Introduction Using HTTP ....................................................................... 20 Getting status and configurations ................................. 20 TA - ToC - Hidden About this guide .................................................................. 4 The top menu bar and the entries in the Table of Sending commands and configurations ........................ 20 text anchor User documentation ........................................................ 4 Contents are all hyperlinks, just click on them to Using HTTP POST ......................................................... 20 go to the topic. About the API Feedback from codec over HTTP ......................................21 Registering for feedback ................................................21 API fundamentals ................................................................ 9 Translating from terminal mode to XML ......................... 22 We recommend you visit our web site regularly for Connecting to the API ..................................................... 9 updated versions of the user documentation. Go to: Password ........................................................................
    [Show full text]
  • (2) G: 9 Timeout Error Layer —T
    US007831732B1 (12) United States Patent (10) Patent No.: US 7,831,732 B1 Zilist et al. (45) Date of Patent: Nov. 9, 2010 (54) NETWORK CONNECTION UTILITY 6,018,724 A 1/2000 Arent 6,182,139 B1 1/2001 Brendel ...................... TO9,226 (75) Inventors: Ira Zilist, Chicago, IL (US); Daniel 6,338,094 B1* 1/2002 Scott et al. .................. 709/245 Reimann, Mt. Prospect, IL (US); Devin 6,393,581 B1 5, 2002 Friedman et al. 6,731,625 B1 5/2004 Eastep et al. Henkel, Chicago, IL (US); Gurpreet 6,742,015 B1 5/2004 Bowman-Amuah Singh, Clarendon Hills, IL (US) 7,082,454 B1* 7/2006 Gheith ....................... TO9,203 2002/0120800 A1* 8/2002 Sugahara et al. .. ... 710,260 (73) Assignee: Federal Reserve Bank of Chicago, 2004/0010546 A1* 1/2004 Kluget al. ............ ... 709,203 Chicago, IL (US) 2004/0192383 A1* 9, 2004 Zacks et al. ................. 455/557 (*) Notice: Subject to any disclaimer, the term of this patent is extended or adjusted under 35 * cited by examiner U.S.C. 154(b) by 1196 days. Primary Examiner Ario Etienne Assistant Examiner Avi Gold (21) Appl. No.: 11/192,991 (74) Attorney, Agent, or Firm—Brinks Hofer Gilson & Lione (22) Filed: Jul. 29, 2005 (57) ABSTRACT Int. C. (51) A system is disclosed for masking errors that may occur G06F 15/16 (2006.01) during a delay of a client connecting with a server on a (52) U.S. Cl. ........................ 709/237; 709/217; 709/219 network. A connection utility requests a connection with the (58) Field of Classification Search ................
    [Show full text]
  • Windows Command Prompt Cheatsheet
    Windows Command Prompt Cheatsheet - Command line interface (as opposed to a GUI - graphical user interface) - Used to execute programs - Commands are small programs that do something useful - There are many commands already included with Windows, but we will use a few. - A filepath is where you are in the filesystem • C: is the C drive • C:\user\Documents is the Documents folder • C:\user\Documents\hello.c is a file in the Documents folder Command What it Does Usage dir Displays a list of a folder’s files dir (shows current folder) and subfolders dir myfolder cd Displays the name of the current cd filepath chdir directory or changes the current chdir filepath folder. cd .. (goes one directory up) md Creates a folder (directory) md folder-name mkdir mkdir folder-name rm Deletes a folder (directory) rm folder-name rmdir rmdir folder-name rm /s folder-name rmdir /s folder-name Note: if the folder isn’t empty, you must add the /s. copy Copies a file from one location to copy filepath-from filepath-to another move Moves file from one folder to move folder1\file.txt folder2\ another ren Changes the name of a file ren file1 file2 rename del Deletes one or more files del filename exit Exits batch script or current exit command control echo Used to display a message or to echo message turn off/on messages in batch scripts type Displays contents of a text file type myfile.txt fc Compares two files and displays fc file1 file2 the difference between them cls Clears the screen cls help Provides more details about help (lists all commands) DOS/Command Prompt help command commands Source: https://technet.microsoft.com/en-us/library/cc754340.aspx.
    [Show full text]
  • Fortianalyzer
    Network diagnose fortilogd Device message rate msgrate-device Network Troubleshooting diagnose fortilogd msgrate-type Message rate for each log type execute ping [host] Ping utility execute traceroute [host] Traceroute utility diag sniffer packet <interface> Packet sniffer Disk <filter> <level> <timestamp> Disk / RAID / Virtual Disk config system fortiview settings Resolve IP address to hostname set resolve-ip enable config system locallog disk setting What happens with oldest logs set diskfull nolog / overwrite Logging diagnose system raid [option] RAID information status, hwinfo, alarms Log Forwarding diagnose system disk [option] Disk information info, health, errors, attributes CHEATSHEET config system log-forward edit log-aggregation <id> For virtual machines: provides a list of Forwarding logs to FortiAnalyzer / execute lvm info available disks aggregation-client set mode Syslog / CEF <realtime, execute lvm extend <disk nr.> For virtual machines: Add disk FORTIANALYZER FOR 6.0 aggregation, disable> config system Configure the FortiAnalyzer that receives © BOLL Engineering AG, FortiAnalyzer Cheat Sheet Version 1.1 / 08.02.2019 log-forward-service logs ADOM set accept-aggregation enable ADOM operation Log Backup config system global ADOM settings set adom-status [en/dis] Enable or disable ADOM mode General execute backup logs config system global Set ADOM mode to normal or advanced / Default device information <device name | all> for VDOMs) <ftp | sftp | scp> <server ip> Backup logs to external storage set adom-mode [normal/advanced]
    [Show full text]
  • Introduction to UNIX at MSI June 23, 2015 Presented by Nancy Rowe
    Introduction to UNIX at MSI June 23, 2015 Presented by Nancy Rowe The Minnesota Supercomputing Institute for Advanced Computational Research www.msi.umn.edu/tutorial/ © 2015 Regents of the University of Minnesota. All rights reserved. Supercomputing Institute for Advanced Computational Research Overview • UNIX Overview • Logging into MSI © 2015 Regents of the University of Minnesota. All rights reserved. Supercomputing Institute for Advanced Computational Research Frequently Asked Questions msi.umn.edu > Resources> FAQ Website will be updated soon © 2015 Regents of the University of Minnesota. All rights reserved. Supercomputing Institute for Advanced Computational Research What’s the difference between Linux and UNIX? The terms can be used interchangeably © 2015 Regents of the University of Minnesota. All rights reserved. Supercomputing Institute for Advanced Computational Research UNIX • UNIX is the operating system of choice for engineering and scientific workstations • Originally developed in the late 1960s • Unix is flexible, secure and based on open standards • Programs are often designed “to do one simple thing right” • Unix provides ways for interconnecting these simple programs to work together and perform more complex tasks © 2015 Regents of the University of Minnesota. All rights reserved. Supercomputing Institute for Advanced Computational Research Getting Started • MSI account • Service Units required to access MSI HPC systems • Open a terminal while sitting at the machine • A shell provides an interface for the user to interact with the operating system • BASH is the default shell at MSI © 2015 Regents of the University of Minnesota. All rights reserved. Supercomputing Institute for Advanced Computational Research Bastion Host • login.msi.umn.edu • Connect to bastion host before connecting to HPC systems • Cannot run software on bastion host (login.msi.umn.edu) © 2015 Regents of the University of Minnesota.
    [Show full text]
  • Webserver Cannot Be Started / No Web Access EAGLE20 / Eagleone
    Knowledgebase > Products > Classic Firewalls > Webserver cannot be started / No web access EAGLE20 / EAGLEOne Webserver cannot be started / No web access EAGLE20 / EAGLEOne - 2018-02-09 - Classic Firewalls At the first startup of a brand new EAGLE or at the first startup after “clear certificates” the web certificates are generated. Affected products are EAGLE20 and EAGLEOne in rel. 05.3.00. If the power is removed during the certificate generation is in progress the webserver cannot be started and therefore no web access is possible. The cli command 'show login' displays the following output: !(Hirschmann EAGLE One) #show login Login parameters ---------------- Access per SSH..........................enabled SSH Access port number..................22 DSA Fingerprint for SSH.................""xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:ab:ab:ab:ab:0f "" RSA Fingerprint for SSH.................""xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:5e "" Access per Web (HTTPS)..................disabled Web Access port number (HTTPS)..........443 SNMP version 1..........................disabled SNMP version 2..........................disabled SNMP port number........................161 SNMP over HTTPS tunneling...............disabled RADIUS auth. of SNMP v3 local users.....disabled Inactivity timeout Web (minutes)........5 Inactivity timeout serial (minutes).....5 Inactivity timeout SSH (minutes)........5 Login prompt............................""Hirschmann EAGLE One"" Login banner............................"""" 23: 2013-01-01 01:00:01 [tCfgMgrTask, CRITICAL, WEB-S, 0x02080014] Web Server - start of web server failed 24: 2013-01-01 01:00:01 [tCfgMgrTask, ERROR, WEB-S, 0x02080028] Web Server - directory for https server certificate could not be created Possible solutions: 1. Reformat the flash file system in sysMon1 and to put the operating firmware on the device again.
    [Show full text]
  • SLC Console Manager User Guide Available At
    SLC™ Console Manager User Guide SLC8 SLC16 SLC32 SLC48 Part Number 900-449 Revision J July 2014 Copyright and Trademark © 2014 Lantronix, Inc. All rights reserved. No part of the contents of this book may be transmitted or reproduced in any form or by any means without the written permission of Lantronix. Lantronix is a registered trademark of Lantronix, Inc. in the United States and other countries. SLC, SLB, SLP, SLM, Detector and Spider are trademarks of Lantronix, Inc. Windows and Internet Explorer are registered trademarks of Microsoft Corporation. Firefox is a registered trademark of the Mozilla Foundation. Chrome is a trademark of Google, Inc. All other trademarks and trade names are the property of their respective holders. Warranty For details on the Lantronix warranty replacement policy, please go to our web site at http://www.lantronix.com/support/warranty. Open Source Software Some applications are Open Source software licensed under the Berkeley Software Distribution (BSD) license or the GNU General Public License (GPL) as published by the Free Software Foundation (FSF). Redistribution or incorporation of BSD or GPL licensed software into hosts other than this product must be done under their terms. A machine readable copy of the corresponding portions of GPL licensed source code may be available at the cost of distribution. Such Open Source Software is distributed WITHOUT ANY WARRANTY, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the GPL and BSD for details. A copy of the licenses is available from Lantronix. The GNU General Public License is available at http://www.gnu.org/licenses/.
    [Show full text]
  • Lab - Observing DNS Resolution (Instructor Version) Instructor Note: Red Font Color Or Gray Highlights Indicate Text That Appears in the Instructor Copy Only
    Lab - Observing DNS Resolution (Instructor Version) Instructor Note: Red font color or Gray highlights indicate text that appears in the instructor copy only. Objectives Part 1: Observe the DNS Conversion of a URL to an IP Address Part 2: Observe DNS Lookup Using the Nslookup Command on a Web Site Part 3: Observe DNS Lookup Using the Nslookup Command on Mail Servers Background / Scenario The Domain Name System (DNS) is invoked when you type a Uniform Resource Locator (URL), such as http://www.cisco.com, into a web browser. The first part of the URL describes which protocol is used. Common protocols are Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol over Secure Socket Layer (HTTPS), and File Transfer Protocol (FTP). DNS uses the second part of the URL, which in this example is www.cisco.com. DNS translates the domain name (www.cisco.com) to an IP address to allow the source host to reach the destination host. In this lab, you will observe DNS in action and use the nslookup (name server lookup) command to obtain additional DNS information. Work with a partner to complete this lab. Required Resources 1 PC (Windows 7, Vista, or XP with Internet and command prompt access) Part 1: Observe the DNS Conversion of a URL to an IP Address a. Click the Windows Start button, type cmd into the search field, and press Enter. The command prompt window appears. b. At the command prompt, ping the URL for the Internet Corporation for Assigned Names and Numbers (ICANN) at www.icann.org. ICANN coordinates the DNS, IP addresses, top-level domain name system management, and root server system management functions.
    [Show full text]
  • Blue Coat SGOS Command Line Interface Reference, Version 4.2.3
    Blue Coat® Systems ProxySG™ Command Line Interface Reference Version SGOS 4.2.3 Blue Coat ProxySG Command Line Interface Reference Contact Information Blue Coat Systems Inc. 420 North Mary Ave Sunnyvale, CA 94085-4121 http://www.bluecoat.com/support/contact.html [email protected] http://www.bluecoat.com For concerns or feedback about the documentation: [email protected] Copyright© 1999-2006 Blue Coat Systems, Inc. All rights reserved worldwide. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of Blue Coat Systems, Inc. All right, title and interest in and to the Software and documentation are and shall remain the exclusive property of Blue Coat Systems, Inc. and its licensors. ProxySG™, ProxyAV™, CacheOS™, SGOS™, Spyware Interceptor™, Scope™, RA Connector™, RA Manager™, Remote Access™ are trademarks of Blue Coat Systems, Inc. and CacheFlow®, Blue Coat®, Accelerating The Internet®, WinProxy®, AccessNow®, Ositis®, Powering Internet Management®, The Ultimate Internet Sharing Solution®, Permeo®, Permeo Technologies, Inc.®, and the Permeo logo are registered trademarks of Blue Coat Systems, Inc. All other trademarks contained in this document and in the Software are the property of their respective owners. BLUE COAT SYSTEMS, INC. DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL BLUE COAT SYSTEMS, INC., ITS SUPPLIERS OR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF BLUE COAT SYSTEMS, INC.
    [Show full text]
  • Shells and Shell Scripting
    Shells and Shell scripting What is a Shell? • A shell is a command line interpreter that is the interface between the user and the OS. • A “program launcher” of sorts. • The shell: o analyzes each command o determines what actions are to be performed o performs the actions • Example: wc –l file1 > file2 Which shell? • sh – Bourne shell o Most common, other shells are a superset o Good for programming • csh or tcsh – default for command line on CDF o C-like syntax o Best for interactive use. Not good for programming. • bash – default on Linux (Bourne again shell) o Based on sh, with some csh features. • korn – written by David Korn o Based on sh – Some claim best for programming. o Commercial product. Common shell facilities Shell startup When a shell is invoked, it does the following: 1. Read a special startup file (usually in home directory) 2. display prompt and wait for command 3. Ctrl-D on its own line terminates shell, otherwise, goto step 2. Shell startup files used to set shell options, set up environment variables, alias sh – executes .profile if it’s there. ksh – executes .profile if in interactive mode. Executes $ENV (usually $HOME/.kshrc) csh – executes .cshrc if it exists. If a login shell, executes .login bash – executes .bashrc, if a login shell, executes .bash_profile instead Executables vs. built-in commands Most commands you run are other compiled programs. Found in /bin Example: ls – shell locates ls binary in /bin directory and launches it Some are not compiled programs, but built into the shell: cd, echo Input-output redirection prog < infile > outfile ls > outfile 2>&1 # sh stdout and stderr Pipelining commands send the output from one command to the input of the next: ls -l | wc ps –aux | grep reid | sort Before a program is executed, the shell recognizes the special characters such as <, >, |, and rewires the standard input, output, or error file descriptors of the program about to be executed to point to the right files (or the standard input of another program).
    [Show full text]