Author(s):	Mark Smith
Location	MCC6
Date	jan Thu 31	Days Raw Files
Start	13:20	First Raw Start	error-in-template
Duration	1:40:00	Offset	None
End	15:00	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2013.linux.org.au/schedule/30277/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Systems_Administration_Server_and_Process_Behavior.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	It would be wonderful if servers and programs would just work and never break. Until that magical day, though, we need to be prepared. Whether you are a junior sysadmin new to the trade or an engineer at a startup who also has to run servers, this tutorial has something for you. We will be covering the basics of gathering information about a server, what it's doing, and how to do seat-of-the-pants estimates on performance. We will discuss and analyze servers misbehaving in typical ways as well as get some ideas on useful ways to think about debugging a server. From there we will do some exercises in spotting problems and debugging running processes. We will also explore side-channel analysis as a tool for intuiting what a process is doing. Typical failure patterns will be discussed and analyzed, and you will have a chance to do some hands-on debugging. Requirements: a laptop, an SSH client, and a basic knowledge of Linux and how to use a shell (bash/zsh). markdown
Comment:	production notes