Your search query "linkto:"AfsOsd/Debugging"" didn't return any results. Please change some terms and refer to HelpOnSearching for more information.
(!) Consider performing a full-text search with your search terms.

Clear message

Contents

  1. Farm node access
    1. Use screen
    2. Open safe shells
    3. Launch test processes
    4. Switch to nodes
  2. Bisecting OpenAFS
    1. Creating the repository
    2. Starting the bisection
    3. Work cycle
    4. Troubleshooting

Farm node access

Use screen

pallas # screen

Open safe shells

From within screen 

pallas # for node in galaxy1 galaxy2 ... ; do screen -t $node ssh $node ; done

Launch test processes

From within screen 

pallas # for node in galaxy1 galaxy2 ... ; do screen -t $node-worker ssh $node /path/to/test-script ; done

Switch to nodes

In screen, enter C-a "

Then select the desired shell from the list.

Bisecting OpenAFS

Do this with a git clone. Really!

Creating the repository

In my case: 

% git clone http://openafs-git.stanford.edu/openafs-test-20090528.git
% cd openafs-test-20090528
% ./regen.sh

Starting the bisection

% git git bisect start openafs-stable-1_4_10 openafs-stable-1_4_8

Work cycle

  1. Compile the current state (preferably from a build host, with repo in AFS) 

    % mkdir `sys` && cd `sys` && ../configure ... && make

    (It can also make sense to build somewhere else entirely, filesystem-wise. Use absolute path to configure then.)

  2. Install and test. If the bug is not yet observed: 

    % git bisect good

    And if it is: 

    % git bisect bad
  3. Configure again, as Makefile.in may have changed here or there...

Troubleshooting

If an intermediate revision won't build or work, you can