|
|
325.
|
|
|
The <emphasis>ErrorDocument</emphasis> directive allows you to specify a file for Apache to use for specific error events. For example, if a user requests a resource that does not exist, a 404 error will occur, and per Apache2's default configuration, the file <filename>/usr/share/apache2/error/HTTP_NOT_FOUND.html.var </filename> will be displayed. That file is not in the server's DocumentRoot, but there is an Alias directive in <filename>/etc/apache2/apache2.conf</filename> that redirects requests to the /error directory to <filename>/usr/share/apache2/error/</filename>.
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
ZhongHan Cai
|
|
|
|
|
348.
|
|
|
Apache is a modular server. This implies that only the most basic functionality is included in the core server. Extended features are available through modules which can be loaded into Apache. By default, a base set of modules is included in the server at compile-time. If the server is compiled to use dynamically loaded modules, then modules can be compiled separately, and added at any time using the LoadModule directive. Otherwise, Apache must be recompiled to add or remove modules.
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
ZhongHan Cai
|
|
|
|
|
361.
|
|
|
There is a default HTTPS configuration file in <filename>/etc/apache2/sites-available/default-ssl</filename>. In order for <application>Apache</application> to provide HTTPS, a <emphasis>certificate</emphasis> and <emphasis>key</emphasis> file are also needed. The default HTTPS configuration will use a certificate and key generated by the <application>ssl-cert</application> package. They are good for testing, but the auto-generated certificate and key should be replaced by a certificate specific to the site or server. For information on generating a key and obtaining a certificate see <xref linkend="certificates-and-security"/>
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
ZhongHan Cai
|
|
|
|
|
362.
|
|
|
To configure <application>Apache</application> for HTTPS, enter the following:
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
ZhongHan Cai
|
|
|
|
|
365.
|
|
|
With Apache now configured for HTTPS, restart the service to enable the new settings:
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
ZhongHan Cai
|
|
|
|
|
575.
|
|
|
There are several ways to automate the Ubuntu installation process, for example using preseeds, kickstart, etc. Refer to the <ulink url="https://help.ubuntu.com/9.10/installation-guide/">Ubuntu Installation Guide</ulink> for details.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
675.
|
|
|
As this example is based on <application>KVM</application> and Ubuntu 9.10 (Karmic Koala), and we are likely to rebuild the same virtual machine multiple time, we'll invoke vmbuilder with the following first parameters:
|
|
|
|
|
(no translation yet)
|
|
|
|
|
676.
|
|
|
sudo vmbuilder kvm ubuntu --suite karmic --flavour virtual --arch i386 -o --libvirt qemu:///system
|
|
|
|
|
(no translation yet)
|
|
|
|
|
694.
|
|
|
sudo vmbuilder kvm ubuntu --suite karmic --flavour virtual --arch i386 -o --libvirt qemu:///system --ip 192.168.0.100
|
|
|
|
|
(no translation yet)
|
|
|
|
|
712.
|
|
|
sudo vmbuilder kvm ubuntu --suite karmic --flavour virtual --arch i386 \ -o --libvirt qemu:///system --ip 192.168.0.100 --part vmbuilder.partition
|
|
|
|
|
(no translation yet)
|
|
|
