page_title: SULinks page_touched: 20140625004850 old_text: ==AWS Console== * http://aws-console-idg.stanford.edu

==Firewall and Network== * Network Reports https://itservices.stanford.edu/service/network/sunet_reports https://www.stanford.edu/group/networking/monitor/n2x/switches.html lists all Net-to-Jack and Net-to-Switch ports, such as the Polya building, but not the machine room networks https://www.stanford.edu/group/networking/monitor/mmr/switches.html lists the Managed Machine Room switches. This does not include the firewall switches.
https://www.stanford.edu/group/networking/monitor/fws/switches.html lists the firewall switches

==Notes==

===Recover an AFS Volume===

An interrupted volume move resulted in the volume disappearing from the input server and not making it to the target server. The following steps will recover the situation.

1. The problem move:

      /usr/bin/vos move -v data.tingliu afssvr14 /vicepa afssvr12 /vicepb
   

2. Recover the volume from its backup. Run:

      vos dump -id data.tingliu.backup -file <path-to-tmp-file>
   

3. Restore the volume and examine the data.

      vos restore -server afssvr12 -part /vicepb -name data.tingliu.fixed -file <path-to-tmp-file>
   

4. Confirm that data.tingliu looks like it has the right contents, and then do:

      vos remove data.tingliu and a vos rename of data.tingliu.fixed to data.tingliu.
   

===Directory Links=== * Description of the Data Owner Approval Process * LDAP Cookbook http://wiki.suretec.org/openldap:cookbook * Memory Segments To examine: ipcs -m To remove: ipcrm -m

===gdb notes===

To get a backtrace of the threads:

thr apply all bt

LDAP FAQ describing how to file bug report: http://www.openldap.org/faq/index.cgi?_highlightWords=gdb&file=59

===git===

====git work flow====

For debian packaging of where the git repo is used for both package tar ball releases and debian packaging I follow Russ Allbery's methods using a debian, master, and upstream branch. The master branch is there changes are made. Changes are exported to an tar ball and imported to the upstream branch. Then the branch is merged into the debian branch for building. To create the tar ball a command of the form works:

    git archive --format=tar.gz HEAD > ../stanford-whois_1.3.7.orig.tar.gz

====git aliases====

You can actually add new git commands in your local git configuration. It's kind of scary-neat.

 git config --global --add alias.update 'pull --rebase --stat'
 git config --global --add push.default matching

Then you can just run "git update" and it does git pull --rebase --stat.

===OOD - Out of Date===

• To see a list of systems that need to be patched:

   remctl memory-new ood query lastpatch 70
  

===Root Mail===

afs-alerts:             leland.alerts.afs@news, leland.alerts@news
build-alerts:           leland.alerts.build@news, leland.alerts@news
calendar-alerts:        leland.alerts.calendar@news, leland.alerts@news
client-alerts:          leland.alerts.client@news, leland.alerts@news
cluster-alerts:         leland.alerts.cluster@news, leland.alerts@news
directory-alerts:       leland.alerts.directory@news, leland.alerts@news
dns-alerts:             leland.alerts.dns@news, leland.alerts@news
email-alerts:           leland.alerts.email@news, leland.alerts@news
kerberos-alerts:        leland.alerts.kerberos@news, leland.alerts@news
monitoring-alerts:      leland.alerts.monitoring@news, leland.alerts@news
pubsw-alerts:           leland.alerts.pubsw@news, leland.alerts@news
registry-alerts:        leland.alerts.registry@news
registry-alerts-test:   leland.alerts.registry-test@news
remedy-alerts:          leland.alerts.remedy@news, leland.alerts@news
sunetid-alerts:         leland.alerts.sunetid@news, leland.alerts@news
usenet-alerts:          leland.alerts.usenet@news, leland.alerts@news
www-alerts:             leland.alerts.www@news, leland.alerts@news

6. row