DOCSLIB.ORG

Cheatsheet V2.4.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cheatsheet V2.4.Pdf ! ! 2.4!Edition! Cross!reference!processes!with!various!lists:! Scan!a!block!of!code!in!process!or!kernel!memory! psxview! for!imported!APIs:! ! impscan!! Show!processes!in!parent/child!tree:! !!!!Hp/HHpid=PID!!!!!!!!!Process!ID!! pstree! !!!!Hb/HHbase=BASE!!!Base!address!to!scan! & !!!!Hs/HHsize=SIZE!!!!!!!Size!to!scan!from!start!of!base! Process&Information& ! ! Logs&/&Histories& Specify!–o/HHoffset=OFFSET!or!Hp/HHpid=1,2,3!! ! ! Recover!event!logs!(XP/2003):! Display!DLLs:! evtlogs!! ! ! dlllist! !!!!HS/HHsaveHevt!!!!!!!!!!!!!!!!!!!!Save!raw!event!logs! Development!build!and!wiki:! ! !!!!HD/HHdumpHdir=PATH!!!Write!to!this!directory! github.com/volatilityfoundation!! Show!command!line!arguments:! ! ! cmdline! Recover!command!history:! Download!a!stable!release:! ! cmdscan!and!consoles!! volatilityfoundation.org!! Display!details!on!VAD!allocations:! ! ! vadinfo![HHaddr]! Recover!IE!cache/Internet!history:! Read!the!book:! ! iehistory!! artofmemoryforensics.com! Dump!allocations!to!individual!files:! ! ! vaddump!HHdumpHdir=PATH![HHbase]! Show!running!services:! Development!Team!Blog:! ! svcscan!! http://volatilityHlabs.blogspot.com!! Dump!all!valid!pages!to!a!single!file:! !!!!Hv/HHverbose!!!!Show!ServiceDll!from!registry! ! memdump!HHdumpHdir=PATH! ! (Official)!Training!Contact:! ! Networking&Information& Display!open!handles:! [email protected]!! ! handles!! ! Active!info!(XP/2003):! !!!!Ht/HHobjectHtype=TYPE!!!Mutant,!File,!Key,!etc…! Follow:!@volatility! connections!and!sockets!! !!!!Hs/HHsilent!!!!!!!!!!!!!!!!!!!!!!!!!!!Hide!unnamed!handles! Learn:!www.memoryanalysis.net!! ! ! ! Scan!for!residual!info!(XP/2003):! Display!privileges:! connscan!and!sockscan! Basic&Usage& privs!! ! ! !!!!Hr/HHregex=REGEX!!!!!!!!!!!Regex!privilege!name! Network!info!for!Vista,!2008,!and!7:& Typical!command!components:!! !!!!Hs/HHsilent!!!!!!!!!!!!!!!!!!!!!!!!!!!Explicitly!enabled!only! netscan! #!vol.py!Hf![image]!HHprofile=[profile]![plugin]! ! ! ! Display!SIDs:! Display!profiles,!address!spaces,!plugins:! getsids! Kernel&Memory& #!vol.py!HHinfo! ! ! ! Display!environment!variables:! Display!loaded!kernel!modules:! Display!global!commandHline!options:! envars! modules! #!vol.py!HHhelp! ! !& ! PE&File&Extraction& Scan!for!hidden!or!residual!modules:! Display!pluginHspecific!arguments:! modscan! ! #!vol.py![plugin]!HHhelp! ! Specify!HD/HHdumpHdir!to!any!of!these!plugins!to! ! Display!recently!unloaded!modules:& identify!your!desired!output!directory.!! Load!plugins!from!an!external!directory:! unloadedmodules! ! #!vol.py!HHplugins=[path]![plugin]!! ! Dump!a!kernel!module:! ! Display!timers!and!associated!DPCs:& moddump!! Specify!a!DTB!or!KDBG!address:! timers!! !!!!Hr/HHregex=REGEX!!!Regex!module!name!! #!vol.py!HHdtb=[addr]!HHkdbg=[addr]! ! !!!!Hb/HHbase=BASE!!!!!!!Module!base!address!! ! Display!kernel!callbacks,!notification!routines:! ! Specify!an!output!file:! callbacks!! Dump!a!process:! #!vol.py!HHoutputHfile=[file]! !! procdump!! Audit!the!SSDT!& ! !!!!Hm/HHmemory!!!!!!!!!!!Include!memory!slack! ssdt!! ! Image&Identification& !!!!Hv/HHverbose!!!!Check!for!inline!API!hooks! Dump!DLLs!in!process!memory:! & ! dlldump!! Get!profile!suggestions!(OS!and!architecture):! Audit!the!IDT!and!GDT:! !!!!Hr/HHregex=REGEX!!!Regex!module!name!! imageinfo!! idt!(x86!only)! !!!!Hb/HHbase=BASE!!!!!!!Module!base!address!! & gdt!(x86!only)! & Find!and!parse!the!debugger!data!block:! ! kdbgscan! Injected&Code& Audit!driver!dispatch!(IRP)!tables:& ! ! driverirp!! Processes&Listings& Specify!–o/HHoffset=OFFSET!or!Hp/HHpid=1,2,3! !!!!Hr/HHregex=REGEX!!!Regex!driver!name! ! ! ! Basic!active!process!listing:! Find!and!extract!injected!code!blocks:! Display!device!tree!(find!stacked!drivers):! pslist! malfind!! devicetree! ! !!!!HD/HHdumpHdir=PATH!!!!Dump!findings!here!! ! Scan!for!hidden!or!terminated!processes:! ! Print!kernel!pool!tag!usage!stats:! psscan! CrossHreference!DLLs!with!memory!mapped!files:! pooltracker! ! ldrmodules! !!!!!!Ht/HHtags=TAGS!!!!!!!List!of!tags!to!analyze! ! ! !!!!!!HT/HHtagfile=FILE!!!pooltag.txt!for!labels! Copyright!©!2014!The!Volatility!Foundation! ! ! 2.4!Edition! Kernel&Objects& Display!a!type/structure:! Dump!the!contents!of!the!clipboard:! >>>!dt(“_EPROCESS”,!recursive!=!True)! clipboard! ! ! ! Scan!for!driver!objects:! Display!a!type/structure!instance:! Detect!message!hooks!(keyloggers):! driverscan! >>>!dt(“_EPROCESS”,! 0x820c92a0)! messagehooks! ! ! ! ! Scan!for!mutexes:! Create!an!object!in!kernel!space:! Take!a!screen!shot!from!the!memory!dump:! mutantscan!! >>>!thread!=!obj.Object(“_ETHREAD”,!offset!=! screenshot!HHdumpHdir=PATH! !!!!Hs/HHsilent!!!!!Hide!unnamed!mutants! ! 0x820c92a0,!vm!=!addrspace())& ! ! & Display!visible!and!hidden!windows:! Scan!for!used/historical!file!objects:! windows!and!wintree! filescan! Dump&Conversion& ! ! ! Scan!for!symbolic!link!objects!(shows!drive! Create!a!raw!memory!dump!from!a!hibernation,! Strings& mappings):& crash!dump,!firewire!acquisition,!virtualbox,! ! symlinkscan! vmware!snapshot,!hpak,!or!EWF!file:! Use!GNU!strings!or!Sysinternals!strings.exe:& ! imagecopy!–O/HHoutputHimage=FILE! strings!Ha!Htd!FILE!>!strings.txt!! ! Registry& strings!Ha!Htd!Hel!FILE!>>!strings.txt!(Unicode)! Convert!any!of!the!aforementioned!file!types!to!a! ! ! Windows!crash!dump!compatible!with!Windbg:! Display!cached!hives:& strings.exe!Hq!Ho!>!strings.txt!(Windows)! raw2dmp!–O/HHoutputHimage=FILE! hivelist! ! & ! Translate!the!string!addresses:! Print!a!key’s!values!and!data:& API&Hooks&& strings! printkey!! ! !!!!Hs/HHstringHfile=FILE!!!!Input!strings.txt!file! !!!Ho/HHhive_offset=OFFSET!!!Hive!address!(virtual)! Scan!for!API!hooks:! !!!!HS/HHscan!! !!!HK/HHkey=KEY!!!!!!!!!!!!!!!!!!!!!!!!!Key!path!! apihooks!! ! ! !!!!HR/HHskipHkernel!!!!!!!!Don’t!check!kernel!modules! Password&Recovery& Dump!userassist!data:! !!!!HP/HHskipHprocess!!!!!!Don’t!check!processes!! userassist! !!!!HQ/HHquick!!!!!!!!!!!!!!!!!!!!Scan!faster!! & ! ! Dump!LSA!secrets:! Dump!shellbags!information:! Yara&Scanning&& lsadump!! shellbags! ! ! ! Dump!cached!domain!hashes:! Scan!for!Yara!signatures:! Dump!the!shimcache:! cachedump!! yarascan!! shimcache! !!!!Hp/HHpid=PID!!!!!!!!!!!!!!!!!!!!!!!Process!IDs!to!scan!! ! ! !!!!HK/HHkernel!!!!!!!!!!!!!!!!!!!!!!!!!!Scan!kernel!memory! Dump!LM!and!NTLM!hashes:! Timelines& !!!!HY/HHyaraHrules=RULES!!!String,!regex,!bytes,!etc.! hashdump!(x86!only)! & !!!!Hy/HHyaraHfile=FILE!!!!!!!!!!!Yara!rules!file!! ! !!!!HW/HHwide!!!!!!!!!!!!!!!!!!!!!!!!!!!Match!Unicode!strings! Extract!OpenVPN!credentials:! To!create!a!timeline,!create!output!in!body!file! !!!!Hs/HHsize!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Size!of!preview!bytes! openvpn!(github.com/Phaeilo)! format.!Combine!the!data!and!run!sleuthkit’s! ! mactime!to!create!a!CSV!file.! ! ! File&System&Resources& Extract!RSA!private!keys!and!certificates:! timeliner!HHoutput=body!>!time.txt! ! dumpcerts! shellbags!HHoutput=body!>>!time.txt!! Scan!for!MFT!records:! !!!!Hs/HHssl!!!!!!!Parse!certificates!with!openssl!! mftparser!HHoutput=body!>>!time.txt! mftparser!! ! ! !!!!HHoutput=body!!!!Output!body!format! Disk&Encryption&& !!!!HD/HHdumpHdir!!!!Dump!MFTHresident!data!! mactime!–b![time.txt]![Hd]!>!csv.txt! ! ! & Extract!cached!files!(registry!hives,!executables):! Recover!cached!TrueCrypt!passphrases:! Volshell& dumpfiles!! truecryptpassphrase!! ! !!!!HD/HHdumpHdir=PATH!!!!!!!Output!directory!! ! List!processes:! !!!!Hr/HHregex=REGEX!!!!!!!!!!!!!Regex!filename!! Triage!TrueCrypt!artifacts:! >>>!ps()! ! truecryptsummary! ! Parse!USN!journal!records:! ! Switch!contexts!by!pid,!offset,!or!name:! usnparser!(github.com/tomspencer)! Extract!TrueCrypt!master!keys! >>>!cc(pid!=!3028)! & truecryptmaster! >>>!cc(offset!=!0x3eb31340,!physical=True)! GUI&Memory& ! >>>!cc(name!=!“explorer.exe”)! ! Malware&Specific& ! Sessions!(shows!RDP!logins):!! ! Acquire!a!process!address!space!after!using!cc:! sessions! Dump!Zeus/Citadel!RC4!keys:! >>>!process_space!=! ! zeusscan!and!citadelscan! proc().get_process_address_space()! Window!stations!(shows!clipboard!owners):! ! ! wndscan! Find!and!decode!Poison!Ivy!configs:! Disassemble!data!in!an!address!space! ! poisonivyconfig! >>>!dis(address,!length,!space)! Desktops!(find!ransomware):! ! ! Deskscan! Decode!Java!RAT!config:! Dump!bytes,!dwords!or!qwords:! ! javaratscan!(github.com/Rurik)! >>>!db(address,!length,!space)! Display!global!and!session!atom!tables:! ! >>>!dd(address,!length,!space)! atoms!and!atomscan! >>>!dq(address,!length,!space)! ! ! ! ! Copyright!©!2014!The!Volatility!Foundation! ! ! 2.4!Edition! ! ! General!Investigations! Dump!the!system’s!raw!registry!hive!files! dumpfiles!Dp!4!DDregex='(config|ntuser)'!DDignoreDcase!DDname!DD!./! Create!a!Graphviz!diagram!of!processes! psscan!DDoutput=dot!DDoutputDfile=graph.dot! Create!a!color!coded!diagram!of!processes!memory! vadtree!Dp!PID!DDoutput=dot!DDoutputDfile=graph.dot! Translate!an!account!SID!to!user!name! printkey!DK!"Microsoft\\Windows!NT\\CurrentVersion\\ProfileList\\[SID]"!|!grep!ProfileImagePath! List!run!keys!for!HKLM!and!all!users! printkey!DK!"Microsoft\\Windows\\CurrentVersion\\Run"! printkey!DK!"Software\\Microsoft\\Windows\\CurrentVersion\\Run"! Find!Unicode!hostnames!or!URLs! yarascan!DY!"/(www|http).+\.(com|net|org)/"!DDwide![DDkernel]! Find!nullDterminated!ASCII!dot!quad!IP!addresses! yarascan!DY!"/([0D9]{1,3}\.){3}[0D9]{1,3}\x00/"!DDwide![DDkernel]! Locate!and!extract!the!HOSTS!file!to!local!directory! filescan!|!egrep!hosts$!|!awk!'{print!$1}'! ! 0x0000000005e3c6d8! dumpfiles!DQ!0x0000000005e3c6d8!DDname!DD!./! Extract!the!admin!password!hash!
Load more

Recommended publications
  • Process and Memory Management Commands
    Process and Memory Management Commands This chapter describes the Cisco IOS XR software commands used to manage processes and memory. For more information about using the process and memory management commands to perform troubleshooting tasks, see Cisco ASR 9000 Series Aggregation Services Router Getting Started Guide. • clear context, on page 2 • dumpcore, on page 3 • exception coresize, on page 6 • exception filepath, on page 8 • exception pakmem, on page 12 • exception sparse, on page 14 • exception sprsize, on page 16 • follow, on page 18 • monitor threads, on page 25 • process, on page 29 • process core, on page 32 • process mandatory, on page 34 • show context, on page 36 • show dll, on page 39 • show exception, on page 42 • show memory, on page 44 • show memory compare, on page 47 • show memory heap, on page 50 • show processes, on page 54 Process and Memory Management Commands 1 Process and Memory Management Commands clear context clear context To clear core dump context information, use the clear context command in the appropriate mode. clear context location {node-id | all} Syntax Description location{node-id | all} (Optional) Clears core dump context information for a specified node. The node-id argument is expressed in the rack/slot/module notation. Use the all keyword to indicate all nodes. Command Default No default behavior or values Command Modes Administration EXEC EXEC mode Command History Release Modification Release 3.7.2 This command was introduced. Release 3.9.0 No modification. Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task IDs.
    [Show full text]
  • How to Dump and Load
    How To Dump And Load Sometimes it becomes necessary to reorganize the data in your database (for example, to move data from type i data areas to type ii data areas so you can take advantage of the latest features)or to move parts of it from one database to another. The process for doping this can be quite simple or quite complex, depending on your environment, the size of your database, what features you are using, and how much time you have. Will you remember to recreate the accounts for SQL users? To resotre theie privileges? Will your loaded database be using the proper character set and collations? What about JTA? Replication? etc. We will show you how to do all the other things you need to do in addition to just dumping and loading the data in your tables. 1 How To Dump and Load gus bjorklund head groundskeeper, parmington foundation 2 What do we mean by dumping and loading? • Extract all the data from a database (or storage area) • Insert the data into a new database (or storage area) • Could be entire database or part 3 Why do we dump and load? 4 Why do we dump & load? • To migrate between platforms • To upgrade OpenEdge to new version • To repair corruption • To “improve performance” • To change storage area configuration • To defragment or improve “scatter” • To fix a “long rm chain” problem • Because it is October 5 Ways to dump and load • Dictionary • 4GL BUFFER-COPY • Binary • Replication triggers (or CDC) • Table partitioning / 4GL • Incremental by storage area 6 Binary Dump & Load • binary dump files – not "human readable"
    [Show full text]
  • Networker Jukebox Control Command Nsrjb
    Maintenance Procedures NSRJB ( 8 ) NAME nsrjb − NetWorker jukebox control command SYNOPSIS nsrjb [ −C ][−j name ][−s server ][−v ][−f device ][−S slots | −T Ta gs | volume names ] nsrjb −L [ −j name ][−s server ][−gimnqvG ][−Y | −N ][−R | −B ][−b pool ][−f device | −J hostname ][−e forev er ][−c capacity ][−o mode ][−S slots | −T tags | volume names ] nsrjb −l [ −j name ][−s server ][−nvqrG ][−R [ −b pool ]][−f device | −J hostname ][−S slot | −T tags | volume names ] nsrjb −u [ −j name ][−s server ][−qv ][−f device ][−S slot | −T tags | volume names ] nsrjb −I [ −j name ][−s server ][−Evpq ][−I | −f device ][−S slots | −T tags | volume_names ] nsrjb −p [ −j name ][−s server ][−vq ][−f device ][−S slot | −T tag | volume name ] nsrjb −o mode [ −j name ][−s server ][−Y ][−S slots | −T tags | volume names ] nsrjb −H [ −j name ][−s server ][−EHvp ] nsrjb −h [ −j name ][−s server ][−v ] nsrjb −U uses [ −j name ][−s server ][−S slots | −T tags ] nsrjb −V [ −j name ][−s server ] nsrjb −d [ −j name ][−s server ][−v ][−N ][−Y ][−P ports ][−S slots ][−T tags ][volume names ] nsrjb −w [ −j name ][−s server ][−v ][−N ][−Y ][−P ports ][−S slots | −T tags | volume names ] nsrjb −a [ −j name ][−s server ][−vd ][−T tags |[−T tags ] volume names ] nsrjb −x [ −j name ][−s server ][−vwX ][−T tags | −S slots ] nsrjb −F [ −j name ][−s server ][−v ] −f device DESCRIPTION The nsrjb program manages resources in two broad classes of jukeboxes, remotely managed jukeboxes and locally managed jukeboxes. Remotely managed jukeboxes are controlled through an external agent.
    [Show full text]
  • Linux Tutorial Last Updated: September 29 2021 for Windows Users
    VLAAMS SUPERCOMPUTER Innovative Computing CENTRUM for A Smarter Flanders Linux Tutorial Last updated: September 29 2021 For Windows Users Authors: Jasper Devreker (UGent), Ewan Higgs (UGent), Kenneth Hoste (UGent) Acknowledgement: VSCentrum.be Audience: This document is a hands-on guide for using the Linux command line in the context of the UGent HPC infrastructure. The command line (sometimes called ’shell’) can seems daunting at first, but with a little understanding can be very easy to use. Everything you do startsatthe prompt. Here you have the liberty to type in any commands you want. Soon, you will be able to move past the limited point and click interface and express interesting ideas to the computer using the shell. Gaining an understanding of the fundamentals of Linux will help accelerate your research using the HPC infrastructure. You will learn about commands, managing files, and some scripting basics. Notification: In$ commands this tutorial specific commands are separated from the accompanying text: These should be entered by the reader at a command line in a terminal on the UGent-HPC. They appear in all exercises preceded by a $ and printed in bold. You’ll find those actions ina grey frame. Button are menus, buttons or drop down boxes to be pressed or selected. “Directory” is the notation for directories (called “folders” in Windows terminology) or specific files. (e.g., “/user/home/gent/vsc400/vsc40000”) “Text” Is the notation for text to be entered. Tip: A “Tip” paragraph is used for remarks or tips. They can also be downloaded from the VSC website at https://www.vscentrum.be.
    [Show full text]
  • Sqlite Dump Without Schema
    Sqlite Dump Without Schema Rodrick unpeopling thermochemically? Autogamous and burst Emanuel check almost hurry-scurry, though Andre inundated his hominidae request. Rident Cobbie electrocuted very huskily while Chandler remains low-key and sickly. The functions are many popular formats, without sqlite schema dump tables in a good chance of sql will generate text file with up your db clear and create table You who check created tables by following commands fist in command line circuit in SQLite command line sqlite3 gamadb sqlite tables Output. To format the world with sqlite tutorial, without sqlite dump schema and are now i thought i increase the. The database schema in an SQLite database is stored ina special table. Using SQLite MoonPoint Support. Application successfully installed devices without going to dump file called. Sqlite3 mysqlitefiledb sqlite output pathtomyoutputfilesql. How To porter The SQLite Dump Command SQLite Tutorial. Impexpc File Reference ch-wernerde. Sqlite commands before it was able to any given json, without sqlite dump file size is how can execute sql? Convert SQLite database to Postgres database like Science. Whenever the without sqlite schema dump command line consists of the table in the support is the last row in list is highly complex peewee. Ram that schema dump command without actually finding and. Trying to know when concatenating character types are dumped db clear, break if start of. Schema Generator MikroORM. Can also crumb the following command which restrict output the file directly. MySQL How you dump a MySQL database and export schema. SQLite Jason L Froebe Tech tips and How Tos for Fellow.
    [Show full text]
  • Epmp Command Line Interface User Guide
    USER GUIDE ePMP Command Line Interface ePMP Command Line Interface User Manual Table of Contents 1 Introduction ...................................................................................................................................... 3 1.1 Purpose ................................................................................................................................ 3 1.2 Command Line Access ........................................................................................................ 3 1.3 Command usage syntax ...................................................................................................... 3 1.4 Basic information ................................................................................................................. 3 1.4.1 Context sensitive help .......................................................................................................... 3 1.4.2 Auto-completion ................................................................................................................... 3 1.4.3 Movement keys .................................................................................................................... 3 1.4.4 Deletion keys ....................................................................................................................... 4 1.4.5 Escape sequences .............................................................................................................. 4 2 Command Line Interface Overview ..............................................................................................
    [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]
  • 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]
  • Your Guide to Installing and Using Coastal Explorer EXPLORING COASTAL EXPLORER Version 4
    EXPLORING COASTAL EXPLORER Your guide to installing and using Coastal Explorer EXPLORING COASTAL EXPLORER Version 4 Your guide to installing and using Coastal Explorer Copyright © 2017 Rose Point Navigation Systems. All rights reserved. Rose Point Navigation Systems, Coastal Explorer, and Coastal Explorer Network are trademarks of Rose Point Navigation Systems. The names of any other companies and/or products mentioned herein may be the trademarks of their respective owners. WARNINGS: Use Coastal Explorer at your own risk. Be sure to carefully read and understand the user's manual and practice operation prior to actual use. Coastal Explorer depends on information from the Global Position System (GPS) and digital charts, both of which may contain errors. Navigators should be aware that GPS- derived positions are often of higher accuracy than the positions of charted data. Rose Point Navigation Systems does not warrant the accuracy of any information presented by Coastal Explorer. Coastal Explorer is intended to be used as a supplementary aid to navigation and must not be considered a replacement for official government charts, notices to mariners, tide and current tables, and/or other reference materials. The captain of a vessel is ultimately responsible for its safe navigation and the prudent mariner does not rely on any single source of information. The information in this manual is subject to change without notice. Rose Point Navigation Systems 18005 NE 68th Street Suite A100 Redmond, WA 98052 Phone: 425-605-0985 Fax: 425-605-1285 e-mail: [email protected] www.rosepoint.com Welcome to Coastal Explorer Thank you for choosing Coastal Explorer! If you are new to navigation software, but use a computer for anything else, you will find that Coastal Explorer works just like many other Windows applications: you create documents, edit them, save them, print them, etc.
    [Show full text]
  • Checkpointing Under Linux with Berkeley Lab Checkpoint/Restart
    N1GE6 Checkpointing and Berkeley Lab Checkpoint/Restart Liang PENG Lip Kian NG N1GE6 Checkpointing and Berkeley Lab Checkpoint/Restart Liang PENG Lip Kian NG APSTC-TB-2004-005 Abstract: N1GE6, formerly known as Sun Grid Engine, is widely used in HPTC environment for efficient utilization of compute resources. As applications in such environment are generally compute intensive, fault tolerance is required to minimize the impact of hardware failure. N1GE6 has several fault tolerance features and in this report, the focus will be on the checkpointing support and the integration of Berkeley Lab Checkpoint/Restart will be used as an example. Keywords: checkpoint, Grid Engine, blcr Email Address: [email protected] [email protected] Revision History Version Date Comments 1.1 Jul 14, 2004 1.2 Dec 28, 2004 Feedback from Reuti (reuti__at__staff.uni-marburg.de) • Transparent interface is user-level (Table 1). • Update to state diagram (Illustration 2). N1GE6 Checkpointing and Berkeley Lab Checkpoint/Restart Liang PENG Lip Kian NG Asia Pacific Science and Technology Center Sun Microsystems Pte Ltd, Singapore Introduction Checkpointing is the process of writing out the state information of a running application to physical storage periodically. With this feature, an application will be able to restart from the last checkpointed state instead of from the beginning which would have been computationally expensive in HPTC environment. In general, checkpointing tools can be classified into 2 different classes: • Kernel-level – Such tools are built into the kernel of the operating system. During a checkpoint, the entire process space (which tends to be huge) is written to physical storage.
    [Show full text]
  • Section “Common Predefined Macros” in the C Preprocessor
    The C Preprocessor For gcc version 12.0.0 (pre-release) (GCC) Richard M. Stallman, Zachary Weinberg Copyright c 1987-2021 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation. A copy of the license is included in the section entitled \GNU Free Documentation License". This manual contains no Invariant Sections. The Front-Cover Texts are (a) (see below), and the Back-Cover Texts are (b) (see below). (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Table of Contents 1 Overview :::::::::::::::::::::::::::::::::::::::: 1 1.1 Character sets:::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Initial processing ::::::::::::::::::::::::::::::::::::::::::::::: 2 1.3 Tokenization ::::::::::::::::::::::::::::::::::::::::::::::::::: 4 1.4 The preprocessing language :::::::::::::::::::::::::::::::::::: 6 2 Header Files::::::::::::::::::::::::::::::::::::: 7 2.1 Include Syntax ::::::::::::::::::::::::::::::::::::::::::::::::: 7 2.2 Include Operation :::::::::::::::::::::::::::::::::::::::::::::: 8 2.3 Search Path :::::::::::::::::::::::::::::::::::::::::::::::::::: 9 2.4 Once-Only Headers::::::::::::::::::::::::::::::::::::::::::::: 9 2.5 Alternatives to Wrapper #ifndef ::::::::::::::::::::::::::::::
    [Show full text]
  • VNC User Guide 7 About This Guide
    VNC® User Guide Version 5.3 December 2015 Trademarks RealVNC, VNC and RFB are trademarks of RealVNC Limited and are protected by trademark registrations and/or pending trademark applications in the European Union, United States of America and other jursidictions. Other trademarks are the property of their respective owners. Protected by UK patent 2481870; US patent 8760366 Copyright Copyright © RealVNC Limited, 2002-2015. All rights reserved. No part of this documentation may be reproduced in any form or by any means or be used to make any derivative work (including translation, transformation or adaptation) without explicit written consent of RealVNC. Confidentiality All information contained in this document is provided in commercial confidence for the sole purpose of use by an authorized user in conjunction with RealVNC products. The pages of this document shall not be copied, published, or disclosed wholly or in part to any party without RealVNC’s prior permission in writing, and shall be held in safe custody. These obligations shall not apply to information which is published or becomes known legitimately from some source other than RealVNC. Contact RealVNC Limited Betjeman House 104 Hills Road Cambridge CB2 1LQ United Kingdom www.realvnc.com Contents About This Guide 7 Chapter 1: Introduction 9 Principles of VNC remote control 10 Getting two computers ready to use 11 Connectivity and feature matrix 13 What to read next 17 Chapter 2: Getting Connected 19 Step 1: Ensure VNC Server is running on the host computer 20 Step 2: Start VNC
    [Show full text]