2/19/2003 Lecture 3 Computer System Administration Lecture 3 Setup (continued)

Slides:



Advertisements
Similar presentations
Unit 5 – User Administration Randy Marchany VA Tech Computing Center.
Advertisements

Basic Unix system administration
Chapter 9: Understanding System Initialization The Complete Guide To Linux System Administration.
Booting and Shutting Down the UNIX Operating System Arcadio A. Sincero Jr. 6/6/2001 CMSC 691X, Section 6080.
Linux+ Guide to Linux Certification Chapter Nine System Initialization.
FreeBSD startup and repair AfNOG 2007 Abuja, Nigeria Hervey Allen Materials from Brian Candler.
LinuxChix System Startup and Recovery. What happens at startup? ● The BIOS loads and runs the MBR ● A series of "bootstrap" programs are loaded – see.
1 Unix Systems Administration Y. K. Chang Generic Unix Directory Structure /bin /dev /etc /sbin /home /lost+found / Root Dir /dsk /rdsk /term /pts /rmt.
Race Condition Zutao Zhu 10/09/09. Outline Race Condition –Some functions –File format of /etc/passwd and /etc/shadow –Input Redirection Format-string.
Unix Refresher This presentation is an amalgam of presentations by Mark Michael, Randy Marchany and Ed Skoudis. I have edited and added material. Dr. Stephen.
Chapter 2 Accessing Your System and the Common Desktop Environment.
Unix kernel Kernel refers to the core part of an operating system Historically, UNIX kernels are monolithic Newer versions of UNIX allow part of the kernel.
User Account Management WeeSan Lee. Roadmap Add An Account Delete An Account /etc/{passwd,shadow} /etc/group How To Disable An Account? Root Account Q&A.
Chapter 6 Adding New Users. Computer Center, CS, NCTU 2 Steps to add a new user 1.Edit the password and group files >vipw 2.Set an initial password >passwd.
Starting and Stopping Linux. Boot Process BIOS initializes hardware –Loads the boot sector MBR loads the bootloader –Point to kernel Kernel initializes.
System Startup and Shutdown
Linux+ Guide to Linux Certification, Second Edition
Linux System Administration LINUX SYSTEM ADMINISTRATION.
Linux Operations and Administration
Introduction to Linux Installing Linux User accounts and management Linux’s file system.
Booting and boot levels
System Startup & Shutdown Objectives –to interpret the Unix startup and shutdown configuration files –to be able to create a customised run level Contents.
Guide to Linux Installation and Administration, 2e1 Chapter 8 Basic Administration Tasks.
UNIX Startup and Shutdown CSCI N321 – System and Network Administration Copyright © 2000, 2010 by Scott Orr and the Trustees of Indiana University.
Adding New Users User as an entity - username(UID), GID. UID - typically a number for system to identify the user. GID – a number that recognizes a set.
ITI-481: Unix Administration Meeting 3. Today’s Agenda Hands-on exercises with booting and software installation. Account Management Basic Network Configuration.
IT2204: Systems Administration I 1 6b). Introduction to Linux.
Isecur1ty training center Presented by : Eng. Mohammad Khreesha.
Unix System Administration Chapter 6 Adding New Users.
Managing Users Objectives Contents Practicals Summary
ITI-481: Unix Administration Meeting 3 Christopher Uriarte, Instructor Rutgers University Center for Applied Computing Technologies.
Users Greg Porter V1.0, 26 Jan 09. What is a user? Users “own” files and directories Permission based on “ownership” Every user has a User ID (UID) 
System Startup & Shutdown
Managing Users  Each system has two kinds of users:  Superuser (root)  Regular user  Each user has his own username, password, and permissions that.
Chapter 3 & 6 Root Status and users File Ownership Every file has a owner and group –These give read,write, and execute priv’s to the owner, group, and.
Oracle Data Integrator Agents. 8-2 Understanding Agents.
The Saigon CTT Chapter 10 Managing Users. The Saigon CTT  Objectives  Define the requirements for user accounts  Explain group and group accounts 
ITI-481: Unix Administration Meeting 3 Christopher Uriarte, Instructor Rutgers University Center for Applied Computing Technologies.
Password. On a Unix system without Shadow Suite, user information including passwords is stored in the /etc/passwd file. Each line in /etc/passwd is a.
Lecture – Users and groups
Linux Operations and Administration
1. Edit the password and group files > vipw(8), pw(8) 2. Set an initial password > passwd lwhsu 3. Set quota > edquota [-u] lwhsu 4. Create user home.
UNIX Startup and Shutdown CSCI N321 – System and Network Administration Copyright © 2000, 2009 by Scott Orr and the Trustees of Indiana University.
CSC414 “Introduction to UNIX/ Linux” Lecture 6. Schedule 1. Introduction to Unix/ Linux 2. Kernel Structure and Device Drivers. 3. System and Storage.
Chapter 6 Adding New Users. Computer Center, CS, NCTU 2 Steps to add a new user 1.Edit the password and group files >vipw, pw 2.Set an initial password.
Sys Admin Course Service Management Fourie Joubert.
1 Figure 6-5: Turning Off Unnecessary Services Unnecessary Services  Operating system vendors used to install many services by default  This made them.
Managing Users CSCI N321 – System and Network Administration Copyright © 2000, 2011 by Scott Orr and the Trustees of Indiana University.
Lecture 4 & 5: System Architecture  File systems  Devices  File system permissions  Review of Linux runlevels  In-class exercise.
Basic UNIX system administration CS 2204 Class meeting 14 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright
System initialization Unit objectives A.Outline steps necessary to boot a Linux system, configure LILO and GRUB boot loaders, and dual boot Linux with.
Using Networks. Assignment Issues find syntax Permissions HW4 3c /proc vs /tmp vs /var.
This slide deck is for LPI Academy instructors to use for lectures for LPI Academy courses. ©Copyright Network Development Group Module 14 Managing.
System Administration Startup Process. Why Care? ● Every process on your system comes about by following a specific chain of events from the machine startup.
LINUX SYSTEM ADMINISTRATION
System Programming and administration CS 308
Linux Start Sequence Summary
FreeBSD startup and repair
Structure of Unix OS.
Chapter 2 User Management
Adding New Users, Storage, File System
OPS235: Week 1 Installing Linux (Lab1: Investigations 4 - )
SUSE Linux Enterprise Desktop Administration
LINUX SYSTEM ADMINISTRATION
Module 13 System and User Security
Adding New Users Chapter 6.
Administering Users and Groups
Administering Users and Groups
Adding New Users.
Chapter 6 Adding New Users
Presentation transcript:

2/19/2003 Lecture 3 Computer System Administration Lecture 3 Setup (continued)

2/19/2003 Lecture 3 On Your Own ● Machines Have/Will be reinstalled – Following Procedure in first 2 lectures – root passwords will be default ● No further “interference” from me. – You are responsible for: ● Security ● Users ● Packages/Software

2/19/2003 Lecture 3 Passwords ● The passwd(1) program – Same on all 3 architectures – Change the root password!!!!! – As root can change other users passwords.

2/19/2003 Lecture 3 /etc/passwd ● Database of user accounts – Flat-File ● Also standard format – Colon separated – Username – Password (encrypted) – UID – GID

2/19/2003 Lecture 3 Passwd(5) file format (cont) – GECOS field ● Comma Separated ● Name ● Phone number ● Office ● Etc... – Home Directory – Shell

2/19/2003 Lecture 3 Shadow Passwords ● Hides the encrypted form of the password. – Root-only access ● Solaris – /etc/shadow – Additional information (must update both) ● Last change time ● Min change time ● Inactive time ●...

2/19/2003 Lecture 3 Shadow Passwords(cont) ● Irix – /etc/shadow ● Also additional fields (must update both) ● Last change ● Min change ● Inactive ●...

2/19/2003 Lecture 3 FreeBSD Shadow Passwords ● /etc/master.passwd – “master” password file – /etc/passwd is generated from master.passwd ● pwd_mkdb – Hashed databases generated ● /etc/pwd.db (public) ● /etc/spwd.db (shadow/private)

2/19/2003 Lecture 3 man(1) pages ● Unix system self documentation/reference – Sections ● Solaris (/usr/share/man/...) – Section 1: User Commands – Section 2: Kernel Functions – Section 3: Library Functions ● Subsections: aio, c, curses, kstat,... – Section 4: File Formats – Section 5: Standards, Environments, Macros

2/19/2003 Lecture 3 Solaris man(1) Sections (cont) – Section 6: Games and Demos – Section 7: Device and Network Interfaces – Section 9: Device Driver Interfaces ● Requesting a specific manpage – man [-s section] page ● Search path – man -s 1 passwd – man -s 4 passwd

2/19/2003 Lecture 3 FreeBSD man(1) sections ● /usr/share/man ● Section 1: User Commands ● Section 2: Kernel Functions ● Section 3: Library Functions ● Section 4: Device Driver Reference ● Section 5: File Formats ● Section 6: Games

2/19/2003 Lecture 3 FreeBSD man(1) sections ● Section 7: Misc ● Section 8: System Administration Commands ● Section 9: Kernel Programming Reference ● Requesting a specific section: – Man [section] page ● Search path ● Man 5 passwd

2/19/2003 Lecture 3 Irix man(1) sections ● Located in /usr/share/catman – Subdivided ● a_man: Administrative ● g_man: Graphics ● u_man: User ● p_man: Programming – Sections ● Section 1: Shell Commands ● Section 2: Kernel Functions

2/19/2003 Lecture 3 Irix man(1) sections ● Section 3: Library Functions ● Section 4: File Formats ● Section 5: Misc ● Section 6: Games ● Section 7: Devices ● Section 8: System Daemons – Requesting specific sections ● man [section] page – Man 4 passwd

2/19/2003 Lecture 3 System Services ● Securing your System – Stop unnecessary services – Tools ● ps ● netstat ● fstat(FreeBSD)/fuser(Solaris/Irix)

2/19/2003 Lecture 3 Solaris System Startup ● Runlevels (man init) – S/s: Single User – 0: Firmware – 1: Administrative – 2: Multi-user mode – 3: Multi-user+Network share – 4: Free – 5: power-off – 6: reboot

2/19/2003 Lecture 3 Runlevel State Transition ● Startup (initdefault 3) – Runlevel 2 – Runlevel 3

2/19/2003 Lecture 3 Runlevel Scripts ● /etc/rc? ● /etc/rc?.d – /etc/rc2.d – /etc/rc3.d – Scripts typically linked to their real location in /etc/init.d ● Kill Scripts – Begin with K – Executed in alphabetical order – K00foo stop

2/19/2003 Lecture 3 Runlevel Start Scripts ● Start Scripts – Begin with S – Executed in alphabetical order – S99foo start

2/19/2003 Lecture 3 start/stop scripts ● Are ONLY executed on a transition INTO a state – KILL scripts are NOT executed when you leave a state, only the kill scripts of the new state are executed – If you want to have apache only running in runlevel 3 you need to put Kill scripts in any other runlevels (typically 2 and 1)

2/19/2003 Lecture 3 Disabling Scripts ● Delete links and originals in /etc/rc?.d and /etc/init.d – BAD – No record of what was once there, no way to get it back ● Delete /etc/rc?.d/[KS]##foo. – Bad – Can retrieve it, but don't know where it goes.

2/19/2003 Lecture 3 Disabling Scripts (cont) ● Rename it – mv S99foo disabled.S99foo – mv K00foo disabled.K00foo – Doesn't start/stop (doesn't begin with K or S) – Keeps a record – Can be reversed

2/19/2003 Lecture 3 Irix System Startup ● Also runlevel/inittab based ● You can manage irix processes in the same way ● Better way – chkconfig ● chkconfig doesn't know about runlevels – Process typically only started/stopped once, in a specific runlevel

2/19/2003 Lecture 3 Chkconfig ● Seeing whats on and whats off – chkconfig -s ● Setting state – chkconfig [-f]{variable} {on | off} – -f for a new flag ● Create your own! ● State stored in /etc/config – One file/variable (same name as variable) – Optionally “variable.options” (stores options for that variable

2/19/2003 Lecture 3 FreeBSD System Startup ● No Runlevels/inittab – Configuration provided by 'rc.conf', similar to Irix chkconfig

2/19/2003 Lecture 3 rc.conf ● rc.conf – /etc/defaults/rc.conf ● Read first ● information/defaults only ● DO NOT EDIT – Will be overwritten by system upgrades/etc – /etc/rc.conf ● Read second ● Make changes here ● Only need to add specific entries for items you want changed

2/19/2003 Lecture 3 FreeBSD Startup: Customizing ● /usr/local/etc/rc.d – local_startup ● Run like inittab scripts – Alphabetical – {start | stop} – Must end in “.sh” – Disable via: mv foo.sh foo.sh.disabled