| import fcntl | |
| import os | |
| import struct | |
| import subprocess | |
| # Some constants used to ioctl the device file. I got them by a simple C | |
| # program. | |
| TUNSETIFF = 0x400454ca | |
| TUNSETOWNER = TUNSETIFF + 2 |
| Use folowing steps to repackage dep package: | |
| 1: Extract deb package | |
| # dpkg-deb -x <package.deb> <dir> | |
| 2: Extract control-information from a package | |
| # dpkg-deb -e <package.deb> <dir/DEBIAN> | |
| 3. After completed to make changes to the package, repack the deb | |
| # dpkg-deb -b <dir> <new-package.deb> |
| /* | |
| iflist.c : retrieve network interface information thru netlink sockets | |
| (c) Jean Lorchat @ Internet Initiative Japan - Innovation Institute | |
| v1.0 : initial version - Feb 19th 2010 | |
| This file was obtained at the following address : | |
| http://www.iijlab.net/~jean/iflist.c |
| this is a sample of output: | |
| root@percona-db-2:~# iperf -s -u -B 226.94.1.1 -i 1 | |
| ------------------------------------------------------------ | |
| Server listening on UDP port 5001 | |
| Binding to local address 226.94.1.1 | |
| Joining multicast group 226.94.1.1 | |
| Receiving 1470 byte datagrams | |
| UDP buffer size: 122 KByte (default) | |
| ------------------------------------------------------------ |
The ngx_http_core_module module supports embedded variables with names matching the Apache Server variables. First of all, these are variables representing client request header fields, such as $http_user_agent, $http_cookie, and so on. Also there are other variables:
| #!/bin/bash | |
| ## FORSTWOOF UBUNTU PRESEED :: BUILD SCRIPT | |
| # Quit on first error | |
| set -e | |
| # Temporary directory for the build | |
| TMP="/var/tmp/ubuntu-build" |
For those that are unfamiliar with the project, PyPy is an implementation of the Python language that features a JIT Compiler. I have noticed a huge performance benefit in some personal projects by switching to PyPy. I have always been curious how it would perform on a large and complex project like OpenStack, but my early experiments ran into massive roadblocks around broken dependencies.
It has been six months since I last looked, so I figured it was time to try it again. Support has come a long way and, now that lxml is working, we are close enough to get a Proof-of-Concept running. Read on for instructions on running nova with PyPy.
Start out with a base ubuntu 12.04 (precise) install and run devstack. I won't go through the details of getting devstack running here, because there are already instructions on the devstack site.
| #include <stdio.h> | |
| #include <stdint.h> | |
| #include <string.h> | |
| #include <sys/ioctl.h> | |
| #include <sys/stat.h> | |
| #include <net/if.h> | |
| #include <ctype.h> | |
| #define ETHTOOL_GSET 0x1 | |
| #define SIOCETHTOOL 0x8946 |
| # Ubuntu Server automated installation | |
| # by Scott Lowe (scott.lowe@scottlowe.org) | |
| d-i debian-installer/locale string en_US | |
| d-i console-setup/ask_detect boolean false | |
| d-i keyboard-configuration/layoutcode string us | |
| d-i netcfg/choose_interface select eth0 | |
| d-i netcfg/get_hostname string hostname | |
| d-i netcfg/get_domain string domain.com | |
| d-i netcfg/wireless_wep string |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
