DOCSLIB.ORG

Calculating Server Uptime

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Calculating Server Uptime Hey, Scripting Guy! Calculating server uptime p is up and down is down. THE MICROSOFT SCRIPTING GUYS ANSWER Seems rather obvious – ex- U cept, that is, when you’re How can I use the System event talking about server uptime. To know uptime, you need to know downtime. log to find server uptime? Nearly every network administrator is concerned about server uptime. (Ex- it generally makes sense to see what When you subtract one time value cept, that is, when he is worried about type of data is being used. from another, you are left with an in- server downtime.) Most administrators To examine the data the script is stance of a System.TimeSpan object. have uptime goals and need to provide using, you can simply print it to the This means you can choose how to dis- uptime reports to upper management. screen. Here’s what you get: play your uptime information without What’s the big deal? It seems like PS C:\> $wmi.LocalDateTime having to perform a lot of arithmetic. you could use the Win32_Operating- 20080905184214.290000-240 You need only choose which proper- System WMI class, which has two ty to display (and hopefully you count The number seems a bit strange. properties that should make such an your uptime in TotalDays and not in What kind of a date is this? To find out, operation pretty easy: LastBootUp- TotalMilliseconds). The default dis- use the GetType method. The good Time and LocalDateTime. All you need play of the System.TimeSpan object is thing about GetType is that it is near- to do, you think, is subtract the Last- shown here: ly always available. All you need to do BootUptime from the LocalDateTime, is call it. And here’s the source of the Days : 0 and then all is right with the world Hours : 0 problem – the LocalDateTime value is Minutes : 40 and you can even go catch a quick nine Seconds : 55 being reported as a string, not as a Sys- holes before dinner. Milliseconds : 914 tem.DateTime value: Ticks : 24559148010 So you fire up Windows PowerShell TotalDays : 0.0284249398263889 PS C:\> $wmi.LocalDateTime.gettype() TotalHours : 0.682198555833333 to query the Win32_OperatingSystem TotalMinutes : 40.93191335 WMI class and select the properties, as IsPublic IsSerial Name BaseType TotalSeconds : 2455.914801 -------- -------- ---- -------- TotalMilliseconds : 2455914.801 shown here: True True String System.Object The problem with this method is PS C:\> $wmi = Get-WmiObject -Class Win32_ that it only tells you how long the OperatingSystem If you need to subtract one time from server has been up since the last re- PS C:\> $wmi.LocalDateTime - $wmi.LastBootUpTime another time, make sure you’re dealing start. It does not calculate downtime. with time values and not strings. This But when you run these commands, This is where up is down – to calculate is easy to do using the ConvertToDate- you are greeted not with the friend- uptime, first you need to know the Time method, which Windows Power- ly uptime of your server, but by the downtime. Shell adds to all WMI classes: rather mournful error message you see So how do you figure out how long PS C:\> $wmi = Get-WmiObject -Class Win32_ in Figure 1. OperatingSystem the server has been down? To do this, The error message is perhaps a bit you need to know when the server PS C:\> $wmi.ConvertToDateTime($wmi.LocalDateTime) – misleading: “Bad numeric constant.” $wmi.ConvertToDateTime($wmi.LastBootUpTime) starts and when it shuts down. You can Huh? You know what a number is and you know what a constant is, but what does this have to do with time? When confronted with strange er- Figure 1 An error is ror messages, it’s best to look directly returned when trying to at the data the script is trying to parse. subtract WMI UTC time Moreover, with Windows PowerShell, values TechNet Magazine February 2009 71 Hey, Scripting Guy! get this information from the System event log. One of the first processes that starts on your server or worksta- tion is the event log, and one of the last things that stop when a server is shut down is the event log. Each of these start/stop events generates an eventID – 6005 when the event log Figure 2 The event log service starts and 6006 when the event log starts shortly after computer stops. Figure 2 shows an example of startup an event log starting. By gathering the 6005 and 6006 events from the System Log, sort- Figure 3 CalculateSystemUpTimeFromEventLog 3 ing them, and subtracting the starts #--------------------------------------------------------------- from the stops, you can determine the # CalculateSystemUpTimeFromEventLog.ps1 amount of time the server was down # ed wilson, msft, 9/6/2008 # between restarts. If you then subtract # Creates a system.TimeSpan object to subtract date values # Uses a .NET Framework class, system.collections.sortedlist to sort the events from eventlog. that amount from the number of min- # utes during the period of time in ques- #--------------------------------------------------------------- #Requires -version 2.0 tion, you can calculate the percentage Param($NumberOfDays = 30, [switch]$debug) of server uptime. This is the approach if($debug) { $DebugPreference = " continue" } taken in the CalculateSystemUpTi- meFromEventLog.ps1 script, which is [timespan]$uptime = New-TimeSpan -start 0 -end 0 $currentTime = get-Date shown in Figure 3. $startUpID = 6005 The script begins by using the Par- $shutDownID = 6006 $minutesInPeriod = (24*60)*$NumberOfDays am statement to define a couple of $startingDate = (Get-Date -Hour 00 -Minute 00 -Second 00).adddays(-$numberOfDays) command-line parameters whose val- Write-debug "'$uptime $uptime" ; start-sleep -s 1 ues you can change when you run the write-debug "'$currentTime $currentTime" ; start-sleep -s 1 script from the command line. The write-debug "'$startingDate $startingDate" ; start-sleep -s 1 first, $NumberOfDays, lets you specify $events = Get-EventLog -LogName system | a different number of days to use in the Where-Object { $_.eventID -eq $startUpID -OR $_.eventID -eq $shutDownID ` -and $_.TimeGenerated -ge $startingDate } uptime report. (Note that I have sup- plied a default value of 30 days in the write-debug "'$events $($events)" ; start-sleep -s 1 script so you can run the script with- $sortedList = New-object system.collections.sortedlist out having to supply a value for the parameter. Of course, you can change ForEach($event in $events) { this if necessary.) $sortedList.Add( $event.timeGenerated, $event.eventID ) } #end foreach event The second, [switch]$debug, is a $uptime = $currentTime - $sortedList.keys[$($sortedList.Keys.Count-1)] switched parameter that lets you ob- Write-Debug "Current uptime $uptime" tain certain debugging information For($item = $sortedList.Count-2 ; $item -ge 0 ; $item -- ) from the script if you include it on { Write-Debug "$item `t `t $($sortedList.GetByIndex($item)) `t ` the command line when running the $($sortedList.Keys[$item])" script. This information can help you if($sortedList.GetByIndex($item) -eq $startUpID) { feel more confident in the results you $uptime += ($sortedList.Keys[$item+1] - $sortedList.Keys[$item]) Write-Debug "adding uptime. `t uptime is now: $uptime" get from the script. There could be } #end if times when the 6006 event log serv- } #end for item ice-stopping message is not present, "Total up time on $env:computername since $startingDate is " + "{0:n2}" -f ` perhaps as a result of a catastrophic $uptime.TotalMinutes + " minutes." $UpTimeMinutes = $Uptime.TotalMinutes failure of the server that rendered it $percentDownTime = "{0:n2}" -f (100 - ($UpTimeMinutes/$minutesInPeriod)*100) unable to write to the event log, caus- $percentUpTime = 100 - $percentDowntime ing the script to subtract an uptime "$percentDowntime% downtime and $percentUpTime% uptime." value from another uptime value and skew the results. 72 Visit TechNet Magazine online at: http://technet.microsoft.com/en-gb/magazine/default.aspx After the $debug variable is supplied erals. The get eventIDs are equal either from the command line, it is present to $startUpID or to $shutDownID. You on the Variable: drive. In that case, the should also make sure the timeGener- value of the $debugPreference varia- ated property of the event log entry is ble is set to continue, which means the greater than or equal to the $starting- script will continue to run and any val- Date, like so: ue supplied to Write-Debug will be vis- $events = Get-EventLog -LogName system | ible. Note that, by default, the value of Where-Object { $_.eventID -eq $startUpID -OR $_.eventID -eq $shutDownID -and $debugPreference is silentlycontinue, $_.TimeGenerated -ge $startingDate } so if you don’t set the value of $debug- Keep in mind that this command Preference to continue, the script will will only run locally. In Windows run, but any value supplied to Write- PowerShell 2.0, you could use the – Debug will be silent (that is, it will not computerName parameter to make be visible). the command work remotely. When the script runs, the resulting Figure 4 Debug mode displays a The next step is to create a sorted list output lists each occurrence of the tracing of each time value that is added to the uptime calculation object. Why? Because when you walk 6005 and 6006 event log entries (as you through the collection of events, you can see in Figure 4) and shows the up- are not guaranteed in which order the time calculation. Using this informa- out the number of minutes during the event log entries are reported. Even if tion, you can confirm the accuracy of period of time in question: you pipeline the objects to the Sort- the results. $minutesInPeriod = (24*60)*$NumberOfDays Object cmdlet and store the results The next step is to create an instance back into a variable, when you iterate of the System.TimeSpan object. You Finally, you need to create the through the objects and store the re- could use the New-Object cmdlet to $startingDate variable, which will hold sults into a hash table, you cannot be create a default timespan object you a System.DateTime object that repre- certain that the list will maintain the would use to perform date-difference sents the starting time of the reporting results of the sort procedure.
Load more

Recommended publications
  • 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]
  • Pingdirectory Administration Guide Version
    Release 7.3.0.3 Server Administration Guide PingDirectory | Contents | ii Contents PingDirectory™ Product Documentation................................................ 20 Overview of the Server............................................................................. 20 Server Features.................................................................................................................................20 Administration Framework.................................................................................................................21 Server Tools Location....................................................................................................................... 22 Preparing Your Environment....................................................................22 Before You Begin.............................................................................................................................. 22 System requirements..............................................................................................................22 Installing Java......................................................................................................................... 23 Preparing the Operating System (Linux).......................................................................................... 24 Configuring the File Descriptor Limits.................................................................................... 24 File System Tuning.................................................................................................................25
    [Show full text]
  • Chapter 10 SHELL Substitution and I/O Operations
    Chapter 10 SHELL Substitution and I/O Operations 10.1 Command Substitution Command substitution is the mechanism by which the shell performs a given set of commands and then substitutes their output in the place of the commands. Syntax: The command substitution is performed when a command is given as: `command` When performing command substitution make sure that you are using the backquote, not the single quote character. Example: Command substitution is generally used to assign the output of a command to a variable. Each of the following examples demonstrate command substitution: #!/bin/bash DATE=`date` echo "Date is $DATE" USERS=`who | wc -l` echo "Logged in user are $USERS" UP=`date ; uptime` echo "Uptime is $UP" This will produce following result: Date is Thu Jul 2 03:59:57 MST 2009 Logged in user are 1 Uptime is Thu Jul 2 03:59:57 MST 2009 03:59:57 up 20 days, 14:03, 1 user, load avg: 0.13, 0.07, 0.15 10.2 Shell Input/Output Redirections Most Unix system commands take input from your terminal and send the resulting output back to your terminal. A command normally reads its input from a place called standard input, which happens to be your terminal by default. Similarly, a command normally writes its output to standard output, which is also your terminal by default. Output Redirection: The output from a command normally intended for standard output can be easily diverted to a file instead. This capability is known as output redirection: If the notation > file is appended to any command that normally writes its output to standard output, the output of that command will be written to file instead of your terminal: Check following who command which would redirect complete output of the command in users file.
    [Show full text]
  • The Linux Command Line Presentation to Linux Users of Victoria
    The Linux Command Line Presentation to Linux Users of Victoria Beginners Workshop August 18, 2012 http://levlafayette.com What Is The Command Line? 1.1 A text-based user interface that provides an environment to access the shell, which interfaces with the kernel, which is the lowest abstraction layer to system resources (e.g., processors, i/o). Examples would include CP/M, MS-DOS, various UNIX command line interfaces. 1.2 Linux is the kernel; GNU is a typical suite of commands, utilities, and applications. The Linux kernel may be accessed by many different shells e.g., the original UNIX shell (sh), the TENEX C shell (tcsh), Korn shell (ksh), and explored in this presentation, the Bourne-Again Shell (bash). 1.3 The command line interface can be contrasted with the graphic user interface (GUI). A GUI interface typically consists of window, icon, menu, pointing-device (WIMP) suite, which is popular among casual users. Examples include MS-Windows, or the X- Window system. 1.4 A critical difference worth noting is that in UNIX-derived systems (such as Linux and Mac OS), the GUI interface is an application launched from the command-line interface, whereas with operating systems like contemporary versions of MS-Windows, the GUI is core and the command prompt is a native MS-Windows application. Why Use The Command Line? 2.1 The command line uses significantly less resources to carry out the same task; it requires less processor power, less memory, less hard-disk etc. Thus, it is preferred on systems where performance is considered critical e.g., supercomputers and embedded systems.
    [Show full text]
  • Bash Guide for Beginners
    Bash Guide for Beginners Machtelt Garrels Garrels BVBA <tille wants no spam _at_ garrels dot be> Version 1.11 Last updated 20081227 Edition Bash Guide for Beginners Table of Contents Introduction.........................................................................................................................................................1 1. Why this guide?...................................................................................................................................1 2. Who should read this book?.................................................................................................................1 3. New versions, translations and availability.........................................................................................2 4. Revision History..................................................................................................................................2 5. Contributions.......................................................................................................................................3 6. Feedback..............................................................................................................................................3 7. Copyright information.........................................................................................................................3 8. What do you need?...............................................................................................................................4 9. Conventions used in this
    [Show full text]
  • Multiping Version 3 Product Manual
    MultiPing version 3 Product Manual (c) 2002, 2014 Nessoft, LLC MultiPing (c) 2002, 2014 Nessoft, LLC All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the written permission of the publisher. Products that are referred to in this document may be either trademarks and/or registered trademarks of the respective owners. The publisher and the author make no claim to these trademarks. While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document. Printed: August 2014 Special thanks to: Publisher All the people who contributed to this documention and to the Nessoft, LLC PingPlotter software. Managing Editor Special recognition to: Pete Ness Pierre Schwab Technical Editor Tom Larrow Jeff Murri Jenna Clara Andrea, D.D., Nina Mele Cam M. Larry M. Contents I Table of Contents Part I Welcome 2 Part II Support / Help 4 Part III Licensing 6 Part IV Getting Started 8 1 Things .t.o.. .d..o.. .w...i.t.h.. .M..u..l.t.i.P...i.n..g.
    [Show full text]
  • Docker Windows Task Scheduler
    Docker Windows Task Scheduler Genealogical Scarface glissading, his karyotype outgone inflicts overflowingly. Rudolph is accessorial and suckers languorously as sociologistic Engelbart bridled sonorously and systematises sigmoidally. Which Cecil merchandises so unbelievably that Cole comedowns her suavity? Simple task runner that runs pending tasks in Redis when Docker container. With Docker Content Trust, see will soon. Windows Tip Run applications in extra background using Task. Cronicle is a multi-server task scheduler and runner with a web based front-end UI It handles both scheduled repeating and on-demand jobs targeting any. Django project that you would only fetch of windows task directory and how we may seem. Docker schedulers and docker compose utility program by learning service on a scheduled time, operators and manage your already interact with. You get a byte array elements followed by the target system privileges, manage such data that? Machine learning service Creatio Academy. JSON list containing all my the jobs. As you note have noticed, development, thank deity for this magazine article. Docker-crontab A docker job scheduler aka crontab for. Careful with your terminology. Sometimes you and docker schedulers for task failed job gets silently redirected to get our task. Here you do want to docker swarm, task scheduler or scheduled background tasks in that. Url into this script in one easy to this was already existing cluster created, it retry a little effort. Works pretty stark deviation from your code is followed by searching for a process so how to be executed automatically set. Now docker for windows service container in most amateur players play to pass as.
    [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]
  • Catalyst 9500 Switches)
    System Management Configuration Guide, Cisco IOS XE Gibraltar 16.12.x (Catalyst 9500 Switches) First Published: 2019-07-31 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]
  • System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1
    SUSE Linux Enterprise Server 15 SP1 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1 An administrator's guide for problem detection, resolution and optimization. Find how to inspect and optimize your system by means of monitoring tools and how to eciently manage resources. Also contains an overview of common problems and solutions and of additional help and documentation resources. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xii 1 Available Documentation xiii
    [Show full text]
  • Managing User Accounts and User Environments in Oracle® Solaris 11.3
    Managing User Accounts and User ® Environments in Oracle Solaris 11.3 Part No: E54800 March 2017 Managing User Accounts and User Environments in Oracle Solaris 11.3 Part No: E54800 Copyright © 1998, 2017, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]