notes.yml

---

Website: www.gnulug.org
Meeting Info: 8CT/9ET/6PT PM in 216 Siebel on 2015-09-29
Remote: '+1 (415) 762-9988 - Meeting ID: 983 180 265 <https://zoom.us/j/983180265>'
Mailing List: http://www.acm.uiuc.edu/sigs/33
Facebook: https://www.facebook.com/groups/uiuc.gluug/
Team Chat: slack.gnulug.org (use your @illinois account to sign up)

Group:
- Ohio Linux Fest

Meeting Sections:
  Linux in the News:
  - TBA

  Education/Learning tools:
  - https://twitter.com/climagic
  - https://hashicorp.com/blog/otto.html - successor to vagrant

  Filesystems:
  - TBA

  SSH:
  - Multiplexing SSH connections with ControlMaster
  - What is multiplexing? Why might you want to multiplex your ssh connections? multiplexing (sometimes contracted to muxing) is a method by which multiple analog message signals or digital data streams are combined into one signal over a shared medium. The aim is to share an expensive resource.
  - mkdir ~/.ssh/cm_socket
  - Host *
        ControlMaster auto
        ControlPath ~/.ssh/cm_socket/%r@%h:%p
  - Specify the path to the control socket used for connection sharing. In the path, ‘%h will be substituted by the target host name, %p the port, and %r by the remote login username. It is recommended that any ControlPath used for opportunistic connection sharing include at least %h, %p, and %r. This ensures that shared connections are uniquely identified.
  - This tells your ssh client to always use a ControlMaster on all hosts. 
  - NOTE: You will need to specify -o ControlMaster=no when using ssh to do ssh tunneling otherwise multiple tunnels to a particular host will not work.
  - Because all of your SSH sessions are multiplexed down a single TCP connection initiated by the first SSH session, that first session must stay alive until all of the other sessions are complete.
  Shell:
  - Command Line Magic One-liner: zcat *access_log*.gz |cat - *access_log* |awk '$9==400||$9==413{print $1}' |sort |uniq
  - Use a # to comment/tag a command for easier searching with [Ctrl-r]

  Containers:
  - TBA

  Vim/Emacs:
  - TBA

  C coding:
  - TBA

Talks:
  Small Talks:
    TBA:
    - TBA

  Big Talks:
    Infrastructure:
    - Discussion of our infrastructure, it's technologies (Vagrant, Puppet, Xen Project), and how to contribute and run your own server.