DOCSLIB.ORG

Fireware Command Line Interface Reference V12.6.4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Fireware Command Line Interface Reference V12.6.4 Fireware Command Line Interface Fireware Reference v12.6.4 Command Line Interface Reference v12.6.4 WatchGuard Fireboxes About This Guide Information in this guide is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of WatchGuard Technologies, Inc. Guide revised: 2/22/2021 Copyright, Trademark, and Patent Information Copyright © 1998–2021 WatchGuard Technologies, Inc. All rights reserved. All trademarks or trade names mentioned herein, if any, are the property of their respective owners. Complete copyright, trademark, patent, and licensing information can be found in the Copyright and Licensing Guide, available online: http://www.watchguard.com/wgrd-help/documentation/overview ii Fireware v12.6.4 Table of Contents Fireware Command Line Interface Reference v12.6.4 i About This Guide ii Copyright, Trademark, and Patent Information ii Table of Contents iii Introduction to the CLI 1 About the CLI Reference Guide 1 Command Reference Format 1 Command Reference Notation 2 Special Characters 2 Sample Command References 2 history 3 export 3 Start the Command Line Interface 4 Connect with a Serial Cable 4 Connect with TCP/IP 5 Connect to the CLI on an XTMv Device 5 Enter Commands in the CLI 7 Terminal Commands 7 Get Help 8 help 8 Syntax in Help Output 9 "?" Command 11 Error Handling in the CLI 11 Import and Export Files 12 Command Modes Overview 13 About CLI Command Modes 13 Main Command Mode 14 Configuration Command Mode 14 Interface Command Mode 14 Link Aggregation Command Mode 15 CLI Reference iii Policy Command Mode 15 Common Commands 15 Command Line Interface Prompt 16 Common Commands 17 About Common Commands 17 List of Common Commands 17 Common Command Reference 18 exit 18 help 19 history 20 ! 20 show 20 show access-portal 23 show alias 23 show antivirus 23 show auth-portal 24 show app-control 24 show auth-server 24 show auth-setting 25 show auth-user-group 25 show backup-list 26 show botnet 26 show bovpn-gateway 26 show bovpn-tunnel 26 show bovpn-vif 27 show bovpntls-client 27 show bridge 27 show categories 28 show certificate 28 show cluster 29 show connection 30 show data-loss-prevention 30 iv Fireware v12.6.4 show ddns 30 show device-mgmt-user 31 show external-auth-hotspot 31 show feature-key 31 show fqdn 31 show geolocation 32 show global-setting 32 show gwc 33 show hotspot 34 show hotspot users 34 show interface 34 show intrusion-prevention 35 show ip 35 show link-aggregation 36 show link-monitor 36 show log-cache 36 show log-setting 38 show modem 38 show mvpn-ipsec 38 show mvpn-rule 39 show network-scan 39 show policy-type 39 show pppoe 39 show proposal 40 show proxy-action 40 show quota 40 show reputation-enabled-defense 41 show rule 41 show sd-wan 41 show signature-update 42 show snat 42 show spamblocker 43 CLI Reference v show stp 43 show sys-storage 43 show traffic-management 43 show trusted-ca-certificates 44 show update-history 44 show usb 44 show user-group 45 show users 45 show v6 45 show vlan 46 show vpn-setting 46 show vpn-status 46 show web-server-cert 47 show wireless 47 show wireless rogue-ap 47 Main Command Mode 49 Main Commands 49 Enter the Main Command Mode 50 List of Main Mode Commands 50 Main Command Mode Reference 52 arp flush 52 backup image 52 cache-flush scan 53 cert-request 53 checksum 54 clock 54 cluster 55 configure 56 csfc 56 debug-cli 57 delete 57 device-mgmt-user 58 vi Fireware v12.6.4 diagnose 58 diagnose to 59 diagnose auth-server 59 diagnose cluster 60 diagnose dynroute 60 diagnose fqdn 60 diagnose hardware 61 diagnose vpn 64 dnslookup 68 export 70 fault-report 71 fips 72 fqdn 73 gwc 74 import 75 mgmt-user-unlock 77 no vpn-status 77 password 77 ping 78 ping -6 78 policy-check 79 quota-reset 79 reboot 80 restore 80 rps 81 shutdown 81 signature-update 81 sync 82 sysinfo 82 tcpdump 82 tlsv13 83 traceroute 83 CLI Reference vii trusted-ca-certificates 84 unlock 84 upgrade 85 upgrade certificate 85 usb 86 vpn-tunnel diag-report 88 vpn-tunnel rekey 88 who 88 Configuration Command Mode 91 Configuration Commands 91 Enter the Configuration Command Mode 92 List of Configuration Mode Commands 92 Configuration Command Mode Reference 94 access-portal 94 app-control 101 auth-portal 102 auth-setting 105 botnet 110 bridge 110 cluster 115 data-loss-prevention 119 ddns 119 default-packet-handling 120 device-mgmt-user 122 dnswatch 123 external-auth-hotspot 124 feature-key 126 geolocation 127 global-setting 128 gwc 132 hotspot 142 interface 146 viii Fireware v12.6.4 intrusion-prevention 146 ip 148 link-aggregation 153 link-monitor 153 log-setting 155 logon-disclaimer 160 loopback 161 managed-client 162 mobile-security 164 modem 166 multi-wan 170 netflow 172 network-mode 174 network-scan 177 ntp 177 policy 178 pppoe 178 quota-action 181 quota-exception 181 quota-rule 182 sd-wan 183 signature-update 185 snat 186 snmp 188 static-arp 189 system 190 threat-detection 190 trusted-ca-certificates 191 v6 ip route 191 vlan 192 vpn-setting 197 web-server-cert 199 CLI Reference ix wireless access-point 200 wireless client 204 wireless radio-settings 206 wireless rogue-ap 207 Interface Command Mode 211 Interface Commands 211 Enter the Interface Command Mode 212 List of Interface Mode Commands 212 Interface Command Mode Reference 213 dhcp 213 enable 216 ip 216 link-speed 218 mac-access-control 218 mac-ip-binding 219 mtu 219 name 220 pppoe 220 qos 222 secondary 223 system-dhcp 223 type 224 v6 224 vpn-pmtu 228 Link Aggregation Command Mode 231 Link Aggregation Commands 231 Enter Link Aggregation Command Mode 232 List of Link Aggregation Mode Commands 232 Link Aggregation Command Mode Reference 233 dhcp 233 ip 236 link-speed 236 x Fireware v12.6.4 member 237 mode 237 mtu 238 override-mac 238 pppoe 238 secondary 240 security-zone 241 system-dhcp 242 Policy Command Mode 243 Policy Commands 243 Enter the Policy Command Mode 244 List of Policy Mode Commands 244 Policy Command Mode Reference 246 alias 246 antivirus 249 apply 250 apt-blocker 250 apt-blocker notification 251 auth-server 252 auth-user-group 255 bovpn-gateway 256 bovpn-tunnel 262 bovpn-vif 266 bovpntls-client 275 dynamic-nat 275 ike-v2-shared 276 l2tp 277 mvpn-ikev2 283 mvpn-ipsec 285 mvpn-rule 288 one-to-one-nat 291 policy-tag 292 CLI Reference xi policy-type 293 proposal 294 quarantine-server 294 reputation-enabled-defense 295 rule 295 schedule 304 spamblocker 304 sslvpn 306 traffic-management 310 user-group 311 users 311 xii Fireware v12.6.4 1 Introduction to the CLI About the CLI Reference Guide WatchGuard® Firebox devices include a Command Line Interface (CLI) installed on the hardware. You can connect to the Firebox and use the CLI as an alternative to the Web UI or WatchGuard System Manager software. You can use the CLI with any terminal client that supports SSH2. This section provides information about how to use the command reference in this document. Command Reference Format The syntax section for each command uses this format: A shaded area shows a single syntax for a command that uses the notation described in the subsequent section. After each command, guidance and comments for the command are shown. For commands where a choice is available for a particular portion of the command, all possible options are described. In the case where a command requires no guidance or comments, this area contains the text “No options available.” CLI Reference 1 Introduction to the CLI Command Reference Notation The syntax section of each command uses a standardized format and notation: Notation Meaning bold Bold text indicates commands and keywords that you enter as shown italic Italic text indicates an argument that you provide. Examples include an account name, password, FTP location, or IP address. [x] Square brackets enclose an optional keyword or argument. (x) Parentheses enclose a required keyword or argument. ... An ellipsis (three consecutive periods without spaces) after an element indicates that the element can be repeated. | A vertical line, called a pipe, that is enclosed within braces or square brackets indicates a choice within a set of keywords or arguments. [x|y] Square brackets around keywords or arguments separated by a pipe indicate an optional choice between separate, mutually exclusive options. (x|y) Parentheses around keywords or arguments separated by a pipe indicate a required choice between separate, mutually exclusive options. [x(y|z)] Parentheses and a pipe within square brackets indicate a required choice within an optional element. Special Characters If you must include special characters within a command argument, such as a password, you can enclose the argument in double quotes " " to remove (escape) the special meaning associated with those characters. Example restore image from usb flash-image backup.fxi "configpassfoo&" Sample Command References A command reference provides: n The command n A brief description of the command n The command syntax n Examples, where appropriate The subsequent commands are two sample command references. Where appropriate, the example also includes sample output. 2 Fireware v12.6.4 Introduction to the CLI history Description Display the command history list with line numbers.
Load more

Recommended publications
  • Shutdown Script for Retropie
    Shutdown Script for Retropie Use pin number 5 & 14 for “Shutdown” 1. Update RetroPie: • sudo apt-get update 2. Upgrade RetroPie • sudo apt-get upgrade 3. Install Python • sudo apt-get install python-dev • sudo apt-get install python3-dev • sudo apt-get install gcc • sudo apt-get install python-pip 4. Next you need to get RPi.GPIO: • wget https://pypi.python.org/packages/source/R/RPi.GPIO/RPi.GPIO-0.5.11.tar.gz 5. Extract the packages: • sudo tar -zxvf RPi.GPIO-0.5.11.tar.gz 6. Move into the newly created directory: • cd RPi.GPIO-0.5.11 • 7. Install the module by doing: • sudo python setup.py install • sudo python3 setup.py install 8. Creating a directory to hold your scripts: • mkdir /home/pi/scripts 9. Call our script shutdown.py (it is written in python). Create and edit the script by doing: • sudo nano /home/pi/scripts/shutdown.py The content of the script: Paste it in the blank area #!/usr/bin/python import RPi.GPIO as GPIO import time import subprocess # we will use the pin numbering to match the pins on the Pi, instead of the # GPIO pin outs (makes it easier to keep track of things) GPIO.setmode(GPIO.BOARD) # use the same pin that is used for the reset button (one button to rule them all!) GPIO.setup(5, GPIO.IN, pull_up_down = GPIO.PUD_UP) oldButtonState1 = True while True: #grab the current button state buttonState1 = GPIO.input(5) # check to see if button has been pushed if buttonState1 != oldButtonState1 and buttonState1 == False: subprocess.call("shutdown -h now", shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE) oldButtonState1 = buttonState1 time.sleep(.1) Press CRTL X Then Y and Enter 10.
    [Show full text]
  • The Linux Kernel Module Programming Guide
    The Linux Kernel Module Programming Guide Peter Jay Salzman Michael Burian Ori Pomerantz Copyright © 2001 Peter Jay Salzman 2007−05−18 ver 2.6.4 The Linux Kernel Module Programming Guide is a free book; you may reproduce and/or modify it under the terms of the Open Software License, version 1.1. You can obtain a copy of this license at http://opensource.org/licenses/osl.php. This book is distributed in the hope it will be useful, but without any warranty, without even the implied warranty of merchantability or fitness for a particular purpose. The author encourages wide distribution of this book for personal or commercial use, provided the above copyright notice remains intact and the method adheres to the provisions of the Open Software License. In summary, you may copy and distribute this book free of charge or for a profit. No explicit permission is required from the author for reproduction of this book in any medium, physical or electronic. Derivative works and translations of this document must be placed under the Open Software License, and the original copyright notice must remain intact. If you have contributed new material to this book, you must make the material and source code available for your revisions. Please make revisions and updates available directly to the document maintainer, Peter Jay Salzman <[email protected]>. This will allow for the merging of updates and provide consistent revisions to the Linux community. If you publish or distribute this book commercially, donations, royalties, and/or printed copies are greatly appreciated by the author and the Linux Documentation Project (LDP).
    [Show full text]
  • Adding a Shutdown Button to the Raspberry Pi B+  Version 1
    Welcome, Guest Log in Register Activity Translate Content Search within content, members or groups Search Topics Resources Members Design Center Store All Places > Raspberry Pi > Raspberry Pi Projects > Documents Adding a Shutdown Button to the Raspberry Pi B+ Version 1 Created by ipv1 on Aug 4, 2015 3:05 AM. Last modified by ipv1 on Aug 18, 2015 9:52 AM. Introduction What do you need? Step 1. Setup the RPi Step 2. Connecting the button Step 3. Writing a Python Script Step 4. Adding it to startup Step 5. More to do Introduction For a beginner to the world of raspberry pi, there are a number of projects that can become the start of something big. In this article, I discuss such a simple project which is adding a button that can be used to shutdown the raspberry pi using a bit of software tinkering. I wrote a similar article in 2013 at my blog “embeddedcode.wordpress.com” and its got its share of attention since a lot of people starting out with a single board computer, kept looking for a power button. Additionally, those who wanted a headless system, needed a way to shutdown the computer without the mess of connecting to it over the network or attaching a monitor and keyboard to it. In this article, I revisit the tutorial on how to add a shutdown button while trying to explain the workings and perhaps beginners will find it an amusing to add find more things to do with this little recipe. What do you need? Here is a basic bill of materials required for this exercise.
    [Show full text]
  • Shutdown Policies with Power Capping for Large Scale Computing Systems Anne Benoit, Laurent Lefèvre, Anne-Cécile Orgerie, Issam Raïs
    Shutdown Policies with Power Capping for Large Scale Computing Systems Anne Benoit, Laurent Lefèvre, Anne-Cécile Orgerie, Issam Raïs To cite this version: Anne Benoit, Laurent Lefèvre, Anne-Cécile Orgerie, Issam Raïs. Shutdown Policies with Power Capping for Large Scale Computing Systems. Euro-Par: International European Conference on Parallel and Distributed Computing, Aug 2017, Santiago de Compostela, Spain. pp.134 - 146, 10.1109/COMST.2016.2545109. hal-01589555 HAL Id: hal-01589555 https://hal.archives-ouvertes.fr/hal-01589555 Submitted on 18 Sep 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Shutdown policies with power capping for large scale computing systems Anne Benoit1, Laurent Lef`evre1, Anne-C´ecileOrgerie2, and Issam Ra¨ıs1 1 Univ. Lyon, Inria, CNRS, ENS de Lyon, Univ. Claude-Bernard Lyon 1, LIP 2 CNRS, IRISA, Rennes, France Abstract Large scale distributed systems are expected to consume huge amounts of energy. To solve this issue, shutdown policies constitute an appealing approach able to dynamically adapt the resource set to the actual workload. However, multiple constraints have to be taken into account for such policies to be applied on real infrastructures, in partic- ular the time and energy cost of shutting down and waking up nodes, and power capping to avoid disruption of the system.
    [Show full text]
  • Absolute BSD—The Ultimate Guide to Freebsd Table of Contents Absolute BSD—The Ultimate Guide to Freebsd
    Absolute BSD—The Ultimate Guide to FreeBSD Table of Contents Absolute BSD—The Ultimate Guide to FreeBSD............................................................................1 Dedication..........................................................................................................................................3 Foreword............................................................................................................................................4 Introduction........................................................................................................................................5 What Is FreeBSD?...................................................................................................................5 How Did FreeBSD Get Here?..................................................................................................5 The BSD License: BSD Goes Public.......................................................................................6 The Birth of Modern FreeBSD.................................................................................................6 FreeBSD Development............................................................................................................7 Committers.........................................................................................................................7 Contributors........................................................................................................................8 Users..................................................................................................................................8
    [Show full text]
  • LAB MANUAL for Computer Network
    LAB MANUAL for Computer Network CSE-310 F Computer Network Lab L T P - - 3 Class Work : 25 Marks Exam : 25 MARKS Total : 50 Marks This course provides students with hands on training regarding the design, troubleshooting, modeling and evaluation of computer networks. In this course, students are going to experiment in a real test-bed networking environment, and learn about network design and troubleshooting topics and tools such as: network addressing, Address Resolution Protocol (ARP), basic troubleshooting tools (e.g. ping, ICMP), IP routing (e,g, RIP), route discovery (e.g. traceroute), TCP and UDP, IP fragmentation and many others. Student will also be introduced to the network modeling and simulation, and they will have the opportunity to build some simple networking models using the tool and perform simulations that will help them evaluate their design approaches and expected network performance. S.No Experiment 1 Study of different types of Network cables and Practically implement the cross-wired cable and straight through cable using clamping tool. 2 Study of Network Devices in Detail. 3 Study of network IP. 4 Connect the computers in Local Area Network. 5 Study of basic network command and Network configuration commands. 6 Configure a Network topology using packet tracer software. 7 Configure a Network topology using packet tracer software. 8 Configure a Network using Distance Vector Routing protocol. 9 Configure Network using Link State Vector Routing protocol. Hardware and Software Requirement Hardware Requirement RJ-45 connector, Climping Tool, Twisted pair Cable Software Requirement Command Prompt And Packet Tracer. EXPERIMENT-1 Aim: Study of different types of Network cables and Practically implement the cross-wired cable and straight through cable using clamping tool.
    [Show full text]
  • Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers
    Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers 03-300431 Issue 4 January 2008 © 2008 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full legal page information, please see the complete document, Avaya Legal Page for Software Documentation, Document number 03-600758. To locate this document on the website, simply go to http://www.avaya.com/support and search for the document number in the search box. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. Warranty Avaya Inc.
    [Show full text]
  • Command Reference Guide for Cisco Prime Infrastructure 3.9
    Command Reference Guide for Cisco Prime Infrastructure 3.9 First Published: 2020-12-17 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Pi-Uptimeups How to Use Python
    How to use the Python demo program For Pi-UpTimeUPS and Pi-Zero-UpTime (PiZ-UpTime) boards (The >> line shows the commands to execute). You need to open a command line window to execute these scripts. Step 1 Make sure you have the latest version of the operating system. >> sudo apt-get update >> sudo apt-get dist-upgrade (Skip this step if you DO NOT want to upgrade to Raspbian STRETCH. Doing this will automatically upgrade you to STRETCH. Say Yes to installing updates/upgrades.) >> sudo apt-get upgrade >> sudo apt-get autoclean If the dist-upgrade went through with updates, please reboot the Pi to ensure you have the latest OS and updates. Step 2 In the home directory (or some other location), create a separate folder. >> mkdir some-folder-name (for example, mkdir uptime) >> cd some-folder-name (for example, cd uptime) Use wget and download the python script from the alchemy-power web site. >> wget http://alchemy-power.com/wp-content/uploads/2017/06/GPIO-shutdown-sample.zip This creates a file GPIO-shutdown-sample.zip file. Step 3 Unzip the GPIO-shutdown-sample.zip file using the unzip command >> unzip GPIO-shutdown-sample.zip This creates a GPIO-shutdown-sample.py file. Step 4 Run the program locally from the command line, from the directory where the file GPIO-shutdown- sample.py is located. >> sudo python GPIO-shutdown-sample.py How to use Python Code P a g e | 1 © 2017 Alchemy Power Inc., All Rights reserved. sudo privileges are needed so that when the battery runs low, the software can execute a proper shutdown.
    [Show full text]
  • Daemon Threads
    Daemon threads Your operating system has various threads that provide services to user threads. That’s their sole purpose: to serve user threads. The term originated with the Unix operating system, but most operating systems have them in one form or another, with slightly differing properties. Examples are: • In Unix, crond is job scheduler, running jobs in the background. Line printer daemon lpd manages printer spooling. • In Windows systems, daemons are called Windows services. One such is Prefetch-and-Superfetch, which caches frequently used files and other components to RAM. The DNS Client resolves domain names to IP addresses. • In Java, the garbage collector is a daemon, continuously finding objects that cannot be reached from the Java program and putting the memory they occupy on a “free list” so the memory can be used for some other purpose. We won’t be writing Java programs that use daemon threads. (Look at the next page for a realistic use of a daemon thread.) Nevertheless, a basic understanding of daemons, including where the word came from, is useful. The basic property of a Java daemon thread In Java, suppose your main-program thread is named t. Suppose t creates and starts threads t1, t2, and t3. Suppose also that it has made t3 a daemon (we show how to do this later). Here is the basic difference be- tween t3 and the other threads: When thread t, t1, and t2 die (i.e. complete method run()), daemon thread t3 is killed. Thus, as long as one normal thread is alive, daemon threads stay alive.
    [Show full text]
  • Freebsd Command Reference
    FreeBSD command reference Command structure Each line you type at the Unix shell consists of a command optionally followed by some arguments , e.g. ls -l /etc/passwd | | | cmd arg1 arg2 Almost all commands are just programs in the filesystem, e.g. "ls" is actually /bin/ls. A few are built- in to the shell. All commands and filenames are case-sensitive. Unless told otherwise, the command will run in the "foreground" - that is, you won't be returned to the shell prompt until it has finished. You can press Ctrl + C to terminate it. Colour code command [args...] Command which shows information command [args...] Command which modifies your current session or system settings, but changes will be lost when you exit your shell or reboot command [args...] Command which permanently affects the state of your system Getting out of trouble ^C (Ctrl-C) Terminate the current command ^U (Ctrl-U) Clear to start of line reset Reset terminal settings. If in xterm, try Ctrl+Middle mouse button stty sane and select "Do Full Reset" exit Exit from the shell logout ESC :q! ENTER Quit from vi without saving Finding documentation man cmd Show manual page for command "cmd". If a page with the same man 5 cmd name exists in multiple sections, you can give the section number, man -a cmd or -a to show pages from all sections. man -k str Search for string"str" in the manual index man hier Description of directory structure cd /usr/share/doc; ls Browse system documentation and examples. Note especially cd /usr/share/examples; ls /usr/share/doc/en/books/handbook/index.html cd /usr/local/share/doc; ls Browse package documentation and examples cd /usr/local/share/examples On the web: www.freebsd.org Includes handbook, searchable mailing list archives System status Alt-F1 ..
    [Show full text]
  • Mengenal Sistim Operasi *BSD
    Mengenal Sistim Operasi *BSD Ada banyak sekali tulisan-tulisan yang membahas tentang BSD, baik tulisan mengenai sejarah, system administrasi, sampai penggunaan BSD kepada end-user sebagai desktop. Tulisan ini memperkenalkan BSD sebagai alternatif lain dari Linux untuk memenuhi kebutuhan akan UNIX-like operating system di Indonesia. Dalam tulisan ini pula, dibahas mengenai beberapa hal yang membedakan antara Linux dan BSD, namun tidak memutuskan mana yang paling baik, karena untuk menentukan mana operating system yang paling baik digunakan adalah Anda sendiri. Daftar Isi 1. Sejarah 2. Distribusi Varian BSD 3. Model Pengembangan 4. Integrasi System 5. Software-software di BSD 6. System Administrasi 7. File System 8. Lain-lain 9. Kesimpulan Sejarah Hampir semua orang telah mendengar Linux saat ini. Namun apa itu BSD? BSD adalah singkatan dari Berkeley Software Distribution. BSD pertama kali dibangun dan dikembangkan oleh Computer System Research Group (CSRG) di University of California at Berkeley (UCB), BSD pertama kali keluar pada akhir 1977 sebagai paket tambahan dan patch dari AT&T UNIX version 6, yang mana waktu itu beroperasi pada mesin PDP-11 minicomputer. BSD pada akhirnya banyak memberikan kontribusi berharga pada pengembangan UNIX secara umum. Ada banyak fitur yang pertama kali diperkenalkan oleh BSD dan beberapa diadopsi dari AT&T dan vendor-vendor lainnya. BSD dibuat, dikembangkan, dan digunakan secara BEBAS sebagai perlawanan terhadap lisensi UNIX yang dimiliki oleh AT&T dan oleh karena itu BSD mempunyai lisensi tersendiri yang memungkinkan setiap orang bebas melakukan pengembangan, dan menggunakan source code BSD. Pada tahun 1993, 4.4BSD dirilis sebagai sebuah Operating System yang utuh. Untuk sejarah lengkap BSD di CSRG, mulai sejarah dari jaman kuda, motivasi orang-orang yang pertama kali mengerjakannya, sampai perseteruan lisensi dan hak cipta dengan AT&T, saya mereferensikan Anda untuk membaca tulisan yang dibuat oleh Kirk McKusick, “Twenty Years of Berkeley Unix“.
    [Show full text]