Gl314 Linux Troubleshooting Rhel7 Sles12

Total Page:16

File Type:pdf, Size:1020Kb

Gl314 Linux Troubleshooting Rhel7 Sles12 EVALUATION COPY Unauthorized Reproduction or Distribution Linux Prohibited Troubleshooting Student Workbook EVALUATION COPY Unauthorized Reproduction GL314 or LINUX Distribution TROUBLESHOOTING RHEL7 SLES12 Prohibited The contents of this course and all its modules and related materials, including handouts to audience members, are copyright ©2017 Guru Labs L.C. No part of this publication may be stored in a retrieval system, transmitted or reproduced in any way, including, but not limited to, photocopy, photograph, magnetic, electronic or other record, without the prior written permission of Guru Labs. This curriculum contains proprietary information which is for the exclusive use of customers of Guru Labs L.C., and is not to be shared with personnel other than those in attendance at this course. This instructional program, including all material provided herein, is supplied without any guarantees from Guru Labs L.C. Guru Labs L.C. assumes no liability for damages or legal action arising from the use or misuse of contents or details contained herein. Photocopying any part of this manual without prior written consent of Guru Labs L.C. is a violation of federal law. This manual should not appear to be a photocopy. If you believe that Guru Labs training materials are being photocopied without permission, please email [email protected] or call 1-801-298-5227. Guru Labs L.C. accepts no liability for any claims, demands, losses, damages, costs or expenses suffered or incurred howsoever arising from or in connection with the use of this courseware. All trademarks are the property of their respective owners. Version: GL314S-R7S12-H02 EVALUATION COPY Unauthorized Reproduction or Distribution Prohibited EVALUATION COPY Unauthorized Table of Contents Chapter 1 Recovery: Network Utilities 7 TROUBLESHOOTING METHODOLOGY 1 Lab Tasks 8 The Troubleshooting Mindset 2 1. Recovery Runlevels 9 Evaluating Possible Solutions 3 2. Recovering Damaged MBR 11 Identifying and Implementing Change 4 3. Recover from Deleted Critical Files 15 Define and Follow PoliciesReproduction 5 Working with Others 6 Chapter 4 Finding Documentation 7 TOPIC GROUP 1 1 Finding Help Online 9 Linux Boot Process 2 System Boot Method Overview 3 Chapter 2 systemd System and Service Manager 4 TROUBLESHOOTING TOOLS 1 Modifying systemd services 6 Common Troubleshooting Tools 2 Using systemd 7 RPM Queries 3 Booting Linux on PCs 9 RPM Verification or 4 Troubleshooting With GRUB 2 11 SRPM and spec Files 5 Boot Process Troubleshooting 13 Hardware Discovery Tools Distribution6 Troubleshooting: Linux and Init 14 Configuring New Hardware with hwinfo 7 Process Management 15 strace and ltrace 8 Process Management Tools 16 lsof and fuser 10 Troubleshooting Processes: top 17 ipcs and ipcrm 12 Filesystem Concepts 18 iostat, mpstat, and vmstat 13 Filesystem Troubleshooting 19 Using hdparm to Measure 15 Backup Concepts 21 Troubleshooting with the ip command 16 Backup Troubleshooting 22 Name Resolution 18 ProhibitedBackup Troubleshooting 23 ss/netstat and rpcinfo 20 Lab Tasks 24 nmap 21 1. Troubleshooting Problems: Topic Group 1 25 Netcat 22 tcpdump and wireshark 23 Chapter 5 Lab Tasks 27 TOPIC GROUP 2 1 1. Determining the System's Configuration 28 Networking Tools 2 2. Troubleshooting with rpm 43 Linux Network Interfaces 3 3. Process Related Tools 46 Networking Commands Review 5 4. Network Tools 54 NetworkManager 6 Networking Troubleshooting 8 Chapter 3 Networking Troubleshooting 9 RESCUE ENVIRONMENTS 1 Virtual Interfaces/IP Aliases 10 Diagnostic/Recovery 2 Network Teaming 11 Rescue Procedures 3 Xinetd Concepts 15 Recovery: mount & chroot 4 Xinetd Troubleshooting 16 Recovery Examples 6 TCP Wrappers Concepts 17 ii Unauthorized TCP Wrappers Concepts 18 1. Troubleshooting Problems: Topic Group 4 17 TCP Wrappers Troubleshooting 19 Netfilter/iptablesEVALUATION Concepts 20 Chapter 8 COPY Netfilter/iptables Troubleshooting 21 TOPIC GROUP 5 1 Lab Tasks 22 Kernel Modules 2 1. Troubleshooting Problems: Topic Group 2 23 Kernel Modules Troubleshooting 3 Logical Volume Management 4 Chapter 6 Reproduction Creating Logical Volumes 5 TOPIC GROUP 3 1 LVM Deployment Issues 6 X11 Concepts 2 VG Migration, PV Resizing & Troubeshooting 7 X11 Server Operation 3 Software RAID Overview 9 X11 Troubleshooting 4 RAID Troubleshooting 10 Rsyslog Concepts 6 Multipathing Overview 11 System Logging 7 SAN Multipathing 12 systemd Journal 9 Multipath Configuration 13 systemd Journal's journalctl 11 Multipathing Best Practices 15 Secure Logging with Journal's Log Sealing or 13 LDAP and OpenLDAP 17 Syslog Troubleshooting 15 Troubleshooting OpenLDAP 18 RPM Concepts Distribution16 NIS and NIS+ (YP) 20 RPM Troubleshooting 17 NIS Troubleshooting Aids 21 Common Unix Printing System (CUPS) 18 Lab Tasks 22 CUPS Troubleshooting 20 1. Troubleshooting Problems: Topic Group 5 23 CUPS Troubleshooting 21 at & cron 22 Chapter 9 at & cron Usage 23 TOPIC GROUP 6 1 at & cron Troubleshooting 24 DNS Concepts 2 Lab Tasks 25 ProhibitedDNS Troubleshooting 3 1. Troubleshooting Problems: Topic Group 3 26 DNS Troubleshooting 4 Apache Concepts 5 Chapter 7 Apache Troubleshooting 6 TOPIC GROUP 4 1 Apache Troubleshooting 7 Users and Groups 2 FTP Concepts 8 Users and Groups Troubleshooting 3 FTP Troubleshooting 9 PAM Concepts 4 Squid Concepts 10 PAM Troubleshooting 5 Squid Troubleshooting 11 Filesystem Quotas 6 Lab Tasks 12 Quotas Troubleshooting 7 1. Troubleshooting Problems: Topic Group 6 13 File Access Control Lists 8 FACL Troubleshooting 9 Chapter 10 SELinux Concepts 10 TOPIC GROUP 7 1 SELinux Troubleshooting 12 Samba Concepts 2 SELinux Troubleshooting Continued 14 Samba Troubleshooting 3 Lab Tasks 16 Postfix Concepts 4 iii Unauthorized Postfix Troubleshooting 6 Postfix Troubleshooting 8 IMAP & POP ConceptsEVALUATION9 COPY IMAP/POP Troubleshooting 10 MariaDB 11 MariaDB Troubleshooting 12 Lab Tasks 13 1. Troubleshooting Problems:Reproduction Topic Group 7 14 or Distribution Prohibited iv Unauthorized Typographic ConventionsEVALUATION COPY The fonts, layout, and typographic conventions of this book have been carefully chosen to increase readability. Please take a moment to familiarize yourself with them. A Warning and SolutionReproduction A common problem with computer training and reference materials is the confusion of the numbers "zero" and "one" with the letters "oh" and 0The number OThe letter "ell". To avoid this confusion, this book uses a fixed-width font that makes "zero". "oh". each letter and number distinct. Typefaces Used and Their Meanings The following typeface conventions have been followedor in this book: fixed-width normal ) Used to denote file names and directories. For example, the /etc/passwd file or /etc/sysconfig/Distributiondirectory. Also used for computer text, particularily command line output. 1The number lThe letter "one". "ell". fixed-width italic ) Indicates that a substitution is required. For example, the string stationX is commonly used to indicate that the student is expected to replace X with his or her own station number, such as station3. fixed-width bold ) Used to set apart commands. For example, theProhibited sed command. Also used to indicate input a user might type on the command line. For example, ssh -X station3. fixed-width bold italic ) Used when a substitution is required within a command or user input. For example, ssh -X stationX. fixed-width underlined ) Used to denote URLs. For example, http://www.gurulabs.com/. variable-width bold ) Used within labs to indicate a required student action that is not typed on the command line. Occasional variations from these conventions occur to increase clarity. This is most apparent in the labs where bold text is only used to indicate commands the student must enter or actions the student must perform. v Unauthorized Typographic ConventionsEVALUATION COPY Terms and Definitions Line Wrapping The following format is used to introduce and define a series of terms: Occasionally content that should be on a single line, such as command line input or URLs, must be broken across multiple lines in order to fit deprecate ) To indicate that something is considered obsolete, with on the page. When this is the case, a special symbol is used to indicate the intent of future removal.Reproduction to the reader what has happened. When copying the content, the line frob ) To manipulate or adjust, typically for fun, as opposed to tweak. breaks should not be included. For example, the following hypothetical grok ) To understand. Connotes intimate and exhaustive knowledge. PAM configuration should only take two actual lines: hork ) To break, generally beyond hope of repair. hosed ) A metaphor referring to a Cray that crashed after the password required /lib/security/pam_cracklib.so retry=3a disconnection of coolant hoses. Upon correction, users were assured type= minlen=12 dcredit=2 ucredit=2 lcredit=0 ocredit=2 the system was rehosed. password required /lib/security/pam_unix.so use_authtok mung (or munge) ) Mash Until No Good: to modify a file, often Representing File Edits irreversibly. troll ) To bait, or provoke, an argument, often targetedor towards the File edits are represented using a consistent layout similar to the unified newbie. Also used to refer to a person that regularly trolls. Distribution diff format. When a line should be added, it is shown in bold with a twiddle ) To make small, often aimless, changes. Similar to frob. plus sign to the left. When a line should be deleted, it is shown struck out with a minus sign to the left. When a line should be modified, it When discussing a command, this same format is also used to show and is shown twice. The old version of the line is shown struck out with a describe a list of common or important command options. For example, minus sign to the left. The new version of the line is shown below the the following ssh options: old version, bold and with a plus sign to the left. Unmodified lines are often included to provide context for the edit. For example, the following -X ) Enables X11 forwarding. In older versions of OpenSSH that do describes modification of an existing line and addition of a new line to not include -Y, this enables trusted X11 forwarding.
Recommended publications
  • Administering Unidata on UNIX Platforms
    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
    [Show full text]
  • Linux from Scratch
    Linux From Scratch Version 3.3 Gerard Beekmans Copyright © 1999−2002 by Gerard Beekmans This book describes the process of creating a Linux system from scratch from an already installed Linux distribution, using nothing but the sources of the software that we use. Copyright (c) 1999−2002, Gerard Beekmans All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: • Redistributions in any form must retain the above copyright notice, this list of conditions and the following disclaimer. • Neither the name of "Linux From Scratch" nor the names of its contributors may be used to endorse or promote products derived from this material without specific prior written permission. • Any material derived from Linux From Scratch must contain a reference to the "Linux From Scratch" project. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Dedication This book is dedicated to my loving and supportive wife Beverly Beekmans.
    [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]
  • What Is a Port
    What is a port The Ports Collection is essentially a set of Makefiles, patches, and description files placed in /usr/ports. The port includes instructions on how to build source code, but does not include the actual source code. You can get the source code from a CD-ROM or from the Internet. Source code is distributed in whatever manner the software author desires. Frequently this is a tarred and gzipped file, but it might be compressed with some other tool or even uncompressed. The program source code, whatever form it comes in, is called a ``distfile'' A port skeleton is a minimal set of files that tell your FreeBSD system how to cleanly compile and install a program. Each port skeleton includes: ●A Makefile. The Makefile contains various statements that specify how the application should be compiled and where it should be installed on your system. A distinfo file. This file contains information about the files that must be downloaded to build the port and their checksums, to verify that files have not been corrupted during the download using md5 A files directory. This directory contains patches to make the program compile and install on your FreeBSD system. Patches are basically small files that specify changes to particular files. They are in plain text format, and basically say ``Remove line 10'' or ``Change line 26 to this ...''. Patches are also known as ``diffs'' because they are generated by the diff program. This directory may also contain other files used to build the port. A pkg-descr file. This is a more detailed, often multiple-line, description of the program.
    [Show full text]
  • Session 12C3 a Simplified Interface for Concurrent Processing
    Session 12c3 A Simplified Interface for Concurrent Processing Janet D. Hartman Applied Computer Science Department Illinois State University Normal, IL 61704 Abstract - Teaching the concepts of concurrency is a task library of C functions, the Parallel Library, that can be used requiring an understanding of how the operating system to introduce the concepts of shared memory multiprocessing allocates resources for the processes and how concurrent and message passing, but hide the details of the actual processes may share data. The difficulty of trying to system calls used to implement them. These functions can understand the asynchronous execution behavior of be used to introduce students to the ideas associated with processes is compounded by the need to understand the concurrent processing in many courses, even at the syntax and required parameters for making the system introductory level. The functions are based on the System calls. Providing wrappers for system calls that make more V UNIX system calls for generating processes and intuitive function calls to allocate and manage resources allocating and managing interprocess communication, but can help students understand the issues involved with could easily be modified for similar POSIX functions. shared memory multiprocessing and message passing systems without having to understand the details of the The Parallel Library syntax associated with making the system calls. This paper describes a library of C functions, the Parallel Library, that The Parallel Library contains functions for creating and can be used to introduce the concepts of shared memory terminating processes along with functions for allocating multiprocessing, message passing, and related and managing interprocess communication structures synchronization issues, but hide the details of the actual (shared memory and message queues) along with functions system calls used to implement them.
    [Show full text]
  • Cyber502x Computer Forensics
    CYBER502x Computer Forensics Unit 2: Linux/Unix Forensics Acquisition CYBER 502x Computer Forensics | Yin Pan Investigating Linux/Unix systems • Four basic forensics steps • Collect • Preserve • Analyze • Present (report) CYBER 502x Computer Forensics | Yin Pan Preparation • A tool box (CD or USB) containing trusted forensic tools • A powerful machine with forensic tools installed and clean-wiped hard drive to store acquired evidence. CYBER 502x Computer Forensics | Yin Pan Remember! • Always have your OWN tool sets ready !! • You are dealing with a compromised system • Run tools from your own USB or device • Save the output outside of the compromised system CYBER 502x Computer Forensics | Yin Pan Forensics tools in common • Ensure forensically-sound operations • Process data structure from the image bypassing kernel’s support • Work on both images and live systems CYBER 502x Computer Forensics | Yin Pan Basic imaging steps • Obtain volatile data (including RAM) –According to policy and the case nature • Acquire non-volatile data (image drives and removable media) CYBER 502x Computer Forensics | Yin Pan Acquire volatile information • System information • Memory usage • Running processes • Logged in users • Network connections • Network interface configuration (promiscuous mode?) • …. CYBER 502x Computer Forensics | Yin Pan Volatile Evidence • Most volatile Least volatile Nonvolatile • Memory • Swap space or gagefile • Network status and connections • Processes running • File opening • Hard drive media • Removable media (CD, Zip, USB,
    [Show full text]
  • Linux Kung Fu Introduction
    Linux Kung Fu Introduction What is Linux? What is the difference between a client and a server? What is Linux? ▪ Linux generally refers to a group of Unix-like free and open-source operating system distributions that use the Linux kernel. ▪ Examples of Linux distributions: – Arch Linux – CentOS – Debian – Fedora – Linux Mint – Red Hat Enterprise Linux (RHEL) – Slackware Linux – Ubuntu Servers versus Clients ▪ Servers provide services ▪ Clients consume services ▪ Examples: ▪ Examples: – Database servers – Laptops and personal computers – DHCP servers – Cellular phones – DNS servers – Tablets and iPads – File servers – Mail servers – Web servers The Terminal The Terminal ▪ Your shell prompt can be a useful source of information. ▪ The shell prompt can be customized. – This can be done by changing the variable $PS1. ▪ You enter commands in the terminal. The Terminal ▪ you@ubnetdef:~$ – Username: you – Host name: ubnetdef – Current working directory: ~ – Superuser: No ($) ▪ root@universe:/etc/init.d# – Username: root – Host name: universe – Current working directory: /etc/init.d – Superuser: Yes (#) Basic Linux Commands $ pwd ▪ The pwd command prints the name of the current working directory. – Essentially, it tells you where you are. ▪ $ sjames5@ubnetdef:~$ pwd – /home/sjames5 $ echo ▪ The echo command echoes (or displays) text. – $ echo “I love the terminal!” ▪ The text is sent to standard output by default, but can be redirected. – $ echo “Why did you redirect me?” > redirect.txt $ clear ▪ The clear command clears the terminal’s screen if possible. $ ls ▪ The ls command lists the contents of a directory. – $ ls – $ ls /etc ▪ To include hidden entries: – $ ls -a – $ ls -A ▪ Did you want more information? – $ ls -l ▪ They can even be used together! – $ ls -Al /var $ cd ▪ The cd command can be used to change your current working directory.
    [Show full text]
  • Linux Shell Scripting Cookbook Second Edition
    Linux Shell Scripting Cookbook Second Edition Over 110 practical recipes to solve real-world shell problems, guaranteed to make you wonder how you ever lived without them Shantanu Tushar Sarath Lakshman BIRMINGHAM - MUMBAI Linux Shell Scripting Cookbook Second Edition Copyright © 2013 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: January 2011 Second edition: May 2013 Production Reference: 1140513 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78216-274-2 www.packtpub.com Cover Image by Parag Kadam ([email protected]) Credits Authors Project Coordinator Shantanu Tushar Shiksha Chaturvedi Sarath Lakshman Proofreader Reviewers Linda Morris Rajeshwari K. John C. Kennedy Indexer Hemangini Bari Anil Kumar Sudhendu Kumar Production Coordinator Aravind SV Shantanu Zagade Acquisition Editor Cover Work Kartikey Pandey Shantanu Zagade Lead Technical Editor Ankita Shashi Technical Editors Jalasha D'costa Amit Ramadas Lubna Shaikh About the Authors Shantanu Tushar is an advanced GNU/Linux user since his college days.
    [Show full text]
  • The Unix/Linux Library for Semaphore and Shared Memory Manipulation Programmed by B
    The Unix/Linux Library for Semaphore and Shared Memory Manipulation Programmed by B. Chandrasekara (February 2002) and updated by E. Talagrand and J. Brinkmeier (January 2004) 1. Introduction This library provides a set of functional calls (based on Unix/Linux system calls) for semaphore definitions and operations on semaphores and for a shared memory definition and shared memory access. Download from Carmen Cse2431 at Files into your directory the following files: ssem.h, ssem.c, sshm.h and sshm.c. Then obtain ssem.o and sshm.o using the following compilation commands: gcc –o ssem.o –c ssem.c gcc –o sshm.o –c sshm.c For a program that uses semaphores and a shared memory, the header files ssem.h and sshm.h have to be included into the source code as follows: #include "ssem.h" #include "sshm.h" and the following compilation commands is to be used: gcc –o program program.c ssem.o sshm.o When semaphores or sheared memories are not used in the given program, sem.o or sshm.o, respectively, may be omitted from the above commands. 2. Semaphore Definition and Operations a. int sem_create(int key, int initial_value) This function creates a new semaphore and returns a positive integer (but only if successful). The positive integer is a semaphore identifier to be used in other semaphore functions. The parameter key has to contain a unique value, and a six digit integer is recommended. The parameter initial_value should contain the initial value for the semaphore. b. int sem_open(int key) This function opens an existing semaphore and it returns a positive integer (but only if successful).
    [Show full text]
  • Lecture 08: Interprocess Communication I October 21, 2019 CS631-Advancedprogrammingintheunixenvironment Slide2 System V IPC
    CS631-AdvancedProgrammingintheUNIXEnvironment Slide1 CS631 - Advanced Programming in the UNIX Environment Interprocess Communication I Department of Computer Science Stevens Institute of Technology Jan Schaumann [email protected] https://stevens.netmeister.org/631/ Lecture 08: Interprocess Communication I October 21, 2019 CS631-AdvancedProgrammingintheUNIXEnvironment Slide2 System V IPC Three types of asynchronous IPC originating from System V: Semaphores Shared Memory Message Queues All three use IPC structures, referred to by an identifier and a key; all three are (necessarily) limited to communication between processes on one and the same host. Since these structures are not known by name, special system calls (msgget(2), semop(2), shmat(2), etc.) and special userland commands (ipcrm(1), ipcs(1), etc.) are necessary. Lecture 08: Interprocess Communication I October 21, 2019 CS631-AdvancedProgrammingintheUNIXEnvironment Slide3 System V IPC: Semaphores A semaphore is a counter used to provide access to a shared data object for multiple processes. To obtain a shared resource a process needs to do the following: 1. Test semaphore that controls the resource. 2. If value of semaphore > 0, decrement semaphore and use resource; increment semaphore when done 3. If value == 0 sleep until value > 0 Semaphores are obtained using semget(2), properties controlled using semctl(2), operations on a semaphore performed using semop(2). Lecture 08: Interprocess Communication I October 21, 2019 CS631-AdvancedProgrammingintheUNIXEnvironment Slide4
    [Show full text]
  • Research on UNIX Forensic Analysis
    International Conference on Intelligent Control and Computer Application (ICCA 2016) Research on UNIX Forensic Analysis Lianfu Yin Nahu College, Jiaxing University Jiaxing, Zhejiang 314033, China [email protected] Abstract—UNIX is one of the most mainstream operating systems, it has great practical significance to research the methodology of B. Initial response information preservation UNIX forensic analysis. This paper firstly introduces the method The initial response information can be saved in the to capture the volatile data from UNIX systems, then introduces following ways: the concrete steps and method of UNIX forensic analysis. 1) Save data on the local hard disk; Keywords- computer crime; computer forensics; UNIX 2) Save data in remote media such as floppy disks, USB forensics Analysis drives or tape drives; 3) Manually record information; Ⅰ. INTRODUCTION As UNIX is one of the most common mainstream operating 4) Use netcat (or cryptcat) command, and transfer the systems, it is quite important to analysis the forensic method of located data to the forensic analytical engine through the UNIX system. Before we do forensic analysis, we shall obtain network. forensic data first. Forensics data are divided into two main Try not to save the data on the local hard disk. When we do categories, one is volatile data, and the other is nonvolatile data. data recovery or forensic analysis, the data stored on the local Volatile data are those data which will all disappear when hard disk would overwrite the deleted data located in the computer shuts down. These data are usually in internal unallocated spaces, for these data may provide evidence while memory, mainly including information like the status of the investigating.
    [Show full text]
  • POSIX-2017 Shell & Utilities Utilities
    POSIX-2017 Shell & Utilities Utilities admin - create and administer SCCS files (DEVELOPMENT) ex - text editor alias - define or display aliases expand - convert tabs to spaces ar - create and maintain library archives expr - evaluate arguments as an expression asa - interpret carriage-control characters false - return false value at - execute commands at a later time fc - process the command history list awk - pattern scanning and processing language fg - run jobs in the foreground basename - return non-directory portion of a pathname file - determine file type batch - schedule commands to be executed in a batch queue find - find files bc - arbitrary-precision arithmetic language fold - filter for folding lines bg - run jobs in the background fort77 - FORTRAN compiler (FORTRAN) c99 - compile standard C programs fuser - list process IDs of all processes that have one or more files cal - print a calendar open cat - concatenate and print files gencat - generate a formatted message catalog cd - change the working directory getconf - get configuration values cflow - generate a C-language flowgraph (DEVELOPMENT) get - get a version of an SCCS file (DEVELOPMENT) chgrp - change the file group ownership getopts - parse utility options chmod - change the file modes grep - search a file for a pattern chown - change the file ownership hash - remember or report utility locations cksum - write file checksums and sizes head - copy the first part of files cmp - compare two files iconv - codeset conversion command - execute a simple command id - return
    [Show full text]