DOCSLIB.ORG

Introduction to Freebsd Welcome

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduction to Freebsd Welcome Introduction to FreeBSD Welcome Introduction Pre-SANOG VI Workshop ¡ ¡ Instructors: Helpers Hervey Allen (USA/Chile) DrukNet staff January 10, 2005 Brian Candler (England) Thimphu, Bhutan Level of this session How the class runs Hervey Allen Brian Candler What we'll do today Class Schedule Some Practical Matters This is a 6 day class going from Monday until When we install please use the root Saturday afternoon. We will have a break on password supplied in class. Thursday afternoon starting around 2pm. During the week please do not change the root password. Time Schedule Please do ask questions! Lots of questions! Morning Lunch Afternoon Really -we mean this. 08:45-10:45 13:00-14:00 14:00-16:00 If you don't understand something be sure Break Break you ask for help! This is how you learn. 11:00-13:00 16:00-18:15 Questions? Outline Outline continued ¢ Why FreeBSD. ¢ Configuring a network interface. ¢ The World of FreeBSD. ¢ Shutdown and restart the server – runlevels. ¢ FreeBSD 5.3 installation. ¢ Services and what is running. ¢ ¢ Command line vs. GUI. How to install software: ¢ Configuration via files. £ packages ¢ FreeBSD disk paritioning. £ ports ¢ FreeBSD directory structure. £ source ¢ How FreeBSD boots (man boot). £ cvs ¢ Commands and programs. ¢ File permissions. Commands “chmod” and “chown”. ¢ Create and remove user accounts. ¢ Summary ¢ The vi editor. ¢ More resources. Why FreeBSD? Linux != UNIX A question I'm sure most of you are asking... ==> Sparky says, “Take a look at this discussion:” ws.edu.isoc.org/workshops/2005/pre-SANOG- VI/day1/whyfreebsd.html The World of FreeBSD Installing FreeBSD (5.3) Start here: http://www.freebsd.org/ How can you install? (FreeBSD Handbook section 2.2.6) ¡ A CDROM or DVD RELEASE (5.3 and 4.10 legacy) ¡ Floppy disks (including preconfigued install) STABLE ('beta' code) ¡ An FTP site, going through a firewall, or using CURRENT ('alpha' code) an HTTP proxy, as necessary ¡ Ports An NFS server ¡ Packages A DOS partition on the same computer ¡ Documentation Project A SCSI or QIC tape ¡ FreeBSD Handbook A dedicated parallel or serial connection Command Line vs. GUI Configuration via Files ¡ ¡ To administer a FreeBSD server you can do this In the Windows world most configuration takes entirely from the command line, or “shell”. place inside the Windows Registry files. These are ¡ A Graphical User Interface (GUI) is not necessary binary database files. to provide services (web, email, print, file, ¡ Under FreeBSD (and Linux/Unix) almost all database, etc.) using FreeBSD (or Linux/Unix). configuration is done using text files. ¡ ¡ You can run multiple command line windows Graphical tools to configure services under (shells) at the same time. FreeBSD simply write to a configuration file. ¡ ¡ To use a GUI you must install the X Windows To configure services you usually need to be the system and a desktop environment such as Gnome system admin account, “root”, and you will often or KDE. We'll do this later in the week. edit text files directly. FreeBSD Disk Organization FreeBSD Partition Schemes If you wish to understand how FreeBSD Partition Usage organizes and views disks then read section a Root partition (/) 3.5 of the FreeBSD handbook for an excellent and succinct description. b swap partition If you come to disk partitioning from a c Not used for filesystems. Windows perspective you will find that d Supposedly not often used. UNIX (FreeBSD, Linux, Solaris, etc.) e/f /tmp, /usr, etc... partitions data very effectively and easily. View partition information using “ ” In FreeBSD a “slice” is what you may consider df -h to be a “partition” under Windows. and “swapinfo” FreeBSD Disk Slices FreeBSD Partitions in a Slice You can see more detailed information about Sample Output to view disk slices from your disk slices by just typing “fdisk” “fdisk -s” To see the partitions in a FreeBSD slice use /dev/ad0: 77520 cyl 16 hd 63 sec Part Start Size Type Flags “disklabel /dev/DEV”: 1: 63 8385867 0x0b 0x80 # /dev/ad1s1: 2: 8385930 8385930 0xa5 0x00 8 partitions: 3: 16771860 208845 0x83 0x00 # size offset fstype [fsize bsize bps/cpg] 4: 16980705 61159455 0x0f 0x00 a: 524288 0 4.2BSD 2048 16384 32776 This is a 40GB disk with 3 operating systems spread b: 2045568 524288 swap across four slices. The operating systems include c: 122865057 0 unused 0 0 # "raw" part, don't edit d: 524288 2569856 4.2BSD 2048 16384 32776 Windows 2000 (1), FreeBSD (2), Linux (3) and the 4th e: 524288 3094144 4.2BSD 2048 16384 32776 partition is a DOS swap slice for Windows 2000. f: 119246625 3618432 4.2BSD 2048 16384 28552 FreeBSD Partitions in a Slice cont. FreeBSD Directory Structure To view slice partition information in a more Repeat after me: “human” readable format use “df -h”. This “The command 'man hier' is your friend.” can, however, be misleading. For example: So, why is your FreeBSD disk partition split in Filesystem Size Used Avail Capacity Mounted on /dev/ad1s1a 248M 35M 193M 15% / to “slices”? Largely to separate important devfs 1.0K 1.0K 0B 100% /dev file systems from each other. These /dev/ad1s1e 248M 526K 227M 0% /tmp filesystems are usually represented by /dev/ad1s1f 55G 2.7G 48G 5% /usr /dev/ad1s1d 248M 42M 186M 18% /var specific directories. /dev/ad1s2 55G 15G 38G 28% /data /dev/da0s1 500M 226M 274M 45% /mnt/flash Why not just run with everything in one Use “swapinfo” to see the swap partition: place? That is, everything under root (/). Device 1K-blocks Used Avail Capacity /dev/ad1s1b 1022784 124 1022660 0% FreeBSD Directory Structure cont. A Few FreeBSD Directories Advantages of a single filesystem: Structure of partitions/directories: ¡ Easier to resize if you want to make it larger. ¡ / (“root”) ¡ Easier conceptually for some people. ¡ /usr Advantages of multiple filesystems: ¡ /var ¡ If one system fails other systems can still work: ¡ swap User fills up disk with runaway program. Power failure only damages one file system. Two important directories: ¡ FreeBSD can optimize layout of files based on ¡ /var/tmp the use for the filesystem. ¡ /usr/home ¡ Logical separation of functionality, thus improving security. I.E. root can be read only. “/” Root /usr The root partition is where critical system files Is used for system software like user tools, live, including the programs necessary to compilers, XWindows, and local repositories boot the system in to “single user” mode. under the /usr/local hierarchy. The idea is that this part of the system does not grow or change, but rather stays isolated If one has to expand* this partition for from the rest of the operating system. additional software, then having it separate makes this possible. If you give enough room to /usr and /var, then “/” can be quite small (around 512MB FreeBSD maps user directories to /usr/home. should be safe for now). The one directory that may grow is /tmp, particularly if you run Linux binaries that use /tmp. *We'll discuss this. We don't always install FreeBSD with a separate /usr partition. /var swap This is where files and directories that Swap is where virtual memory lives. Swap is consistently change are kept. For example, it's own filesystem. webserver logs, email directories, print You can run without swap, and your PC may spools, temporary files, etc. run faster, but this is dangerous if you run out of memory. On a server it is a good idea to have /var in a separate partition to avoid having it fill your There are several opinions about what is the optimal swap size. This can depend on what other filesystems by accident. type of services you run (databases need more swap). The general rule of thumb is that swap size should be somewhere between your RAM and twice your server's RAM. How FreeBSD Boots How FreeBSD Boots cont. The init process: The init process cont.: ¡ ¡ After the kernel boots, which is located in “/” (in Once file systems are mounted then the Linux it's usually /boot) it hands over control to following starts: the program /sbin/init. ¡ Networking services ¡ If filesystems look good then init begins reading ¡ System daemons the resource configuration of the system. These ¡ Locally installed package daemons files are read in this order: (/usr/local/etc/rc.d scripts) ¡ /etc/defaults/rc.conf ¡ Init process and shutdown: /etc/rc.conf (overrides previous) ¡ ¡ When shutdown is called then init runs the /etc/rc.conf.local (overrides previous) scripts /etc/rc.shutdown. ¡ Mounts file systems in /etc/fstab Commands - Programs – Shell – Path Basic Commands What's a “command” and a “program”? ¡ cp, cd*, ls, mkdir, mv, rm y man Why can't you always run all commands and ¡ (*built in command shell commands). programs on a system? ¡ Where are commands located? ¡ How do you “fix” this? /bin, /usr/bin, /usr/local/bin, /sbin, /usr/sbin ¡ The difference between “sbin”, “bin” and “ How do you see how things are configured for /usr” a user? ¡ If you know DOS: ¡ /usr/share/skel ¡ cp = copy ¡ /etc/profile ¡ cd/chdir = cd/chdir ¡ ¡ /home/user/.bashrc ls = dir ¡ ¡ /home/user/.bash_profile mkdir = mkdir ¡ ¡ set, printenv, export mv = move (before it was copy and delete/erase) ¡ rm = del[ete] and/or erase Create, Remove, Update User /etc/passwd Accounts (FreeBSD Handbook section 8.6) The /etc/password file has the following User Creation and Maintenance format: ¡ hervey:x:500:500:Hervey passwd, pw, vipw Allen:/home/hervey:/usr/local/bin/bash Some Associated Files i.e.: ¡ /etc/passwd, /etc/group, /etc/master.passwd, user:pw:UID:GID:name:directory:shell /etc/sudoers (note visudo) Using /etc/master.passwd the “pw” is ¡ /usr/share/skel represented by an “x”.
Load more

Recommended publications
  • 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]
  • 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]
  • 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]
  • AIX Security
    AIX Security Jaqui Lynch Mainline Information Systems Email – [email protected] Useblue 3/14/05 htt://www.circle4.com/papers/ubsec05.pdf The purpose of this talk is not to encourage hacking but to assist the system administrator in protecting their systems against hackers. 1 Agenda ¾ Basics – Security Types – Permissions ¾ Freeware/Shareware Tools that can help – TCP Wrappers & Secure Shell – Apache, openssl, modssl, stunnel – Portmap – Snort – Ftp ¾ Logging, finding Rootkits ¾ Scanners and Tools ¾ Questions 2 1 Security Types ¾Physical ¾Local – Keep system patched!!! ¾Files and filesystems ¾Passwords ¾Kernel ¾Network 3 Levels & Types of Attacks ¾ Levels ¾ Types – Embarrassment (replace – Root access break-in banners, home page, – Replacement of etc) materials – Denial of service (syn- flood connections) – Damage done – Ping of Death – Just looking – Stealing proprietary code – Theft of proprietary – Pornography – Harassment or threats - information stalking – Denial of service – Email Spam or bulk – Worms and Trojans subscribes – Hate mail – Buffer Overflow 4 2 SANS Top 20 www.sans.org/top20/#threats 1. U1 BIND/DNS 6. U6 Simple Network Management 1. DOS, buffer overflow, etc Protocol (SNMP) 2. U2 Apache Web Server 1. Public/Private, v1 very insecure 1. Mod_ssl worm, chunk handling 7. U7 Open Secure Sockets Layer exploit, default cgi 1. Multiple exploits 3. U3 General Unix Authentication 8. U8 Misconfiguration of NIS/NFS 1. Accounts with No Passwords or 1. Multiple exploits Weak Passwords 9. U9 Databases 4. U4 Version Control Systems 1. Multiple vulnerabilities in Oracle 1. Anonymous access via port 2401 and MYSQL t0 repository 2. SQL Injection Vulnerabilities in 5. U5 Mail Services Oracle E-Business Suite 1.
    [Show full text]
  • Unix Computer Forensics
    Honeynet2_book.fm Page 347 Thursday, April 29, 2004 11:09 AM UNIX Computer Fo12rensics Brian Carrier In the last chapter, we discussed the basics of computer forensics. In this chapter, we discuss the details for analyzing a UNIX system that is suspected of being compromised. The analysis should identify the evidence you’ll need to determine what the attacker did to the system. This chapter assumes that you have already read the basics provided in Chapter 11, so you should read that chapter first if you haven’t already. As Linux is accessible to many and frequently used as a honeynet system, this sec- tion will focus on the details of a Linux system. The concepts discussed apply to other UNIX flavors, but some of the details, such as file names, may differ. All sections of this chapter include examples from the Honeynet Forensic Challenge, which was released in January of 2001. While the actual rootkits and tools that were installed on this system are now outdated, the approach to analyzing the system is the same. The Challenge images are still commonly used because they are the best public example of an actual incident. You can download them from http://www.honeynet.org/challenge and they are included with the CD-ROM. The tools used in this chapter are all free and Open Source. Therefore, anyone can perform the techniques presented and analyze the Forensic Challenge images. 347 Honeynet2_book.fm Page 348 Thursday, April 29, 2004 11:09 AM C HAPTER 12 UNIX COMPUTER FORENSICS This chapter begins with Linux background information, such as file systems and system configuration.
    [Show full text]
  • LINUX Commands
    LINUX Commands alias Create an alias apropos Search Help manual pages (man -k) awk Find and Replace text, database sort/validate/index break Exit from a loop builtin Run a shell builtin bzip2 Compress or decompress named file(s) cal Display a calendar case Conditionally perform a command cat Display the contents of a file cd Change Directory cfdisk Partition table manipulator for Linux chgrp Change group ownership chmod Change access permissions chown Change file owner and group chroot Run a command with a different root directory cksum Print CRC checksum and byte counts clear Clear terminal screen cmp Compare two files comm Compare two sorted files line by line command Run a command - ignoring shell functions continue Resume the next iteration of a loop cp Copy one or more files to another location cron Daemon to execute scheduled commands crontab Schedule a command to run at a later time csplit Split a file into context-determined pieces cut Divide a file into several parts date Display or change the date & time dc Desk Calculator dd Data Dump - Convert and copy a file ddrescue Data recovery tool declare Declare variables and give them attributes df Display free disk space diff Display the differences between two files diff3 Show differences among three files dig DNS lookup dir Briefly list directory contents dircolors Colour setup for `ls' dirname Convert a full pathname to just a path dirs Display list of remembered directories du Estimate file space usage echo Display message on screen egrep Search file(s) for lines that match an
    [Show full text]
  • Introducing the Command Line April 26Th, 2002
    Mac OS X Command Line 101 by Richard Burton Introducing The Command Line April 26th, 2002 "The truth is rarely pure, and never simple." - Oscar Wilde, The Importance of Being Earnest With the release of OS X, the Macintosh has a command line for the first time since it was introduced in 1984. Admittedly, Apple has done a great job with OS X, and the vast majority of users can go a long time without having to ever touch the terminal. In fact, many of the longtime Mac faithful don't care to learn it at all, but there are growing numbers of people who would like to know how to use it. Mac OS X Command Line 101 is going to try and help those people do just that. While Apple has done a tremendous job with OS X, no operating system is perfect. Sometimes a problem cannot be fixed using one of the standard GUI tools, or sometimes one of those GUI tools doesn't do quite what you want. Sometimes, there are even times when using the command line is just easier. Luckily, OS X is based on Unix. Unix was not market-driven; it was written by geeks for geeks in the real ivory tower of the past, Bell Labs. To understand what this means, consider what Larry Wall, creator of the Perl programming language, calls the three great virtues of programmers: laziness, impatience, and hubris. Laziness means you don't want to spend a lot of time and effort doing something simple, or doing it repeatedly.
    [Show full text]
  • Introduction to Linux
    Introduction to Linux A Hands on Guide Machtelt Garrels CoreSequence.com <[email protected]> Version 1.8 Last updated 20030916 Edition Introduction to Linux Table of Contents Introduction.........................................................................................................................................................1 1. Why this guide?...................................................................................................................................1 2. Who should read this book?.................................................................................................................1 3. New versions of this guide...................................................................................................................1 4. Revision History..................................................................................................................................1 5. Contributions.......................................................................................................................................2 6. Feedback..............................................................................................................................................2 7. Copyright information.........................................................................................................................3 8. What do you need?...............................................................................................................................3 9. Conventions used
    [Show full text]
  • Lsof – List Open Files
    LsofLsof –– ListList OpenOpen FilesFiles O que é o Lsof? Opções Conclusão OO queque éé oo LsofLsof?? Lsof é um comando UNIX que lista informações sobre qualquer arquivo aberto. Um arquivo aberto pode ser um arquivo comum, um diretório, uma biblioteca, um arquivo de rede (soquete de internet, arquivo NFS ou soquete de domínio UNIX) e etc, que foi aberto por um processo que estão rodando no sistema. UmUm exemploexemplo dede saídasaída dodo comandocomando lsoflsof Executando o comando lsof sem opções ele lhe retorna todos o arquivos abertos de todos os processos. Devido a quantidade enorme de linhas que são geralmente exibidas torna-se necessário afunilar sua listagem por meio do uso das várias opções que o lsof possui. Ex.: [root@cyclone /]# lsof COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME init 1 root cwd DIR 3,5 4096 2 / init 1 root rtd DIR 3,5 4096 2 / init 1 root txt REG 3,5 26920 125807 /sbin/init init 1 root mem REG 3,5 85420 109907 /lib/ld-2.2.5.so init 1 root mem REG 3,5 1343176 109916 /lib/libc-2.2.5.so init 1 root 10u FIFO 3,5 37306 /dev/initctl keventd 2 root cwd DIR 3,5 4096 2 / keventd 2 root rtd DIR 3,5 4096 2 / keventd 2 root 10u FIFO 3,5 37306 /dev/initctl kapmd 3 root cwd DIR 3,5 4096 2 / kapmd 3 root rtd DIR 3,5 4096 2 / kapmd 3 root 10u FIFO 3,5 37306 /dev/initctl *Apenas parte do que foi listado está exposto acima (foram exibidas mais de 800 linhas) OpçõesOpções lsof –u <UID>[,login] Lista os arquivos abertos de processos cujo o dono seja o que foi especificado por meio do <UID> (user ID) ou login.
    [Show full text]