Changes between Version 3 and Version 4 of TesterDocumentation
- Timestamp:
- 09/09/10 12:17:32 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TesterDocumentation
v3 v4 1 = Reporting bugs=1 = Building development versions of OpenVPN = 2 2 3 You should document a few things: 3 == Downloading OpenVPN snapshots == 4 4 5 * Operating system (e.g. OpenBSD 4.3) 6 * Your ''./configure'' command-line 7 * The complete output of: 8 {{{ 9 $ openvpn --version 10 }}} 5 There are two ways to get development versions of OpenVPN. First option is to get snapshot builds available here: 11 6 7 * http://build.openvpn.net/downloads/ 12 8 13 = Building OpenVPN testing from git = 9 There are several directories there, one per git branch. New features are available in the [http://build.openvpn.net/downloads/allmerged/ allmerged branch]. [ftp://ftp.secure-computing.net/pub/FreeBSD/ports/openvpn-devel/ Weekly snapshots] of various OpenVPN branches are also available [ftp://ftp.secure-computing.net/pub/FreeBSD/ports/openvpn-devel/ here]. 14 10 15 == Fetching the sources == 11 Once you've downloaded a snapshot package, extract it: 12 13 {{{ 14 gzip -dc openvpn-<something>.tar.gz | tar xvf - 15 cd openvpn-<something>/ 16 }}} 17 18 == Fetching sources using git == 16 19 17 20 * If you have not cloned the git repository: … … 31 34 }}} 32 35 36 == Building == 37 33 38 * Prepare for building: 34 39 … … 36 41 autoreconf -vi 37 42 }}} 38 39 = Building OpenVPN testing from snapshots =40 41 * Download the latest snapshot tarball from: ftp://ftp.secure-computing.net/pub/FreeBSD/ports/openvpn-devel/42 * Unpack it43 44 {{{45 gzip -dc openvpn-YYYYWW.tar.gz | tar xvf -46 cd openvpn-devel/47 }}}48 49 == Configure and compile ==50 43 51 44 When testing this version of OpenVPN, we would appreciate if all deprecated features would be disabled by default. We want to know how OpenVPN behaves for you without these features. … … 70 63 in addition to the ./configure line use used for the compilation and all the configuration files you used. We would like to have both success and fail reports. 71 64 72 65 = Debugging = 73 66 74 67 If OpenVPN crashes, you can help developers figure out the problem by giving them a backtrace of the crash. If you're running released (stable) version of OpenVPN, you should install the ''openvpn debug'' and ''gdb'' packages and then run openvpn via gdb. On "testing" turn on debugging before compilation. In either case you can get a backtrace of the crash like this: … … 83 76 }}} 84 77 85 78 = Enable core dump = 86 79 87 80 In some cases, it's not possible to trigger the bug when running via gdb directly. In this case, you can enable core dumps. On most distributions and *nix OSes today, you need to enable this from your shell before starting OpenVPN. … … 102 95 103 96 Beware that if you start OpenVPN via init scripts, it will most likely not dump core files, unless you change the ulimit inside the init script. 97 98 = Reporting bugs = 99 100 You should document a few things: 101 102 * Operating system (e.g. OpenBSD 4.3) 103 * Your ''./configure'' command-line 104 * The complete output of: 105 {{{ 106 $ openvpn --version 107 }}}