1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
.\" Hey, EMACS: -*- nroff -*-
.TH fai.conf 5 "December 2013" "FAI 4.0"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
.\" .nh disable hyphenation
.\" .hy enable hyphenation
.\" .ad l left justify
.\" .ad b justify to both left and right margins
.\" .nf disable filling
.\" .fi enable filling
.\" .br insert line break
.\" .sp <n> insert n+1 empty lines
.\" for manpage-specific macros, see man(7)
.SH NAME
fai.conf \- FAI Configuration
.SH SYNOPSIS
.B /etc/fai/fai.conf
.SH DESCRIPTION
The configuration for a target host consists of two parts:
.IP \(bu
The
\fINFSROOT\fP, a very basic yet complete root file system,
which is exported to clients.
The NFSROOT is built using
.BR fai-make-nfsroot (8).
.IP \(bu
The
\fIconfiguration space\fP, which is loaded as one of the first steps of a FAI run.
Several tools and protocols are supported for maintaining and accessing the
configuration space.
See
.BR FAI_CONFIG_SRC
below.
.LP
.BR fai.conf
defines the essential options to successfully start a FAI run.
It must be valid
.BR bash (1)
code.
This configuration file is NOT copied into the nfsroot by fai-make-nfsroot.
.SH VARIABLES
.TP
\fBFAI_CONFIG_SRC\fP URL to access configuration space
A protocol-specific URL defining the server and directory/repository to fetch
the configuration space from.
.LP
The following protocols and URL schemes are currently supported:
.IP \(bu
NFS: nfs://<server>/<exported directory>
.IP \(bu
Local directory: file://<directory>
The directory has to be an absolute path. So, this URI always starts
with three slashes like this: file:///
.IP \(bu
CVS: cvs[+ssh]://<user>@<host>/<cvs root> <module>[=<tag>]
.IP \(bu
Subversion: svn[+(file|http|https|ssh)]://[<user>@]<host>/<repository>
.IP \(bu
Git: git[+<protocol>]://<git path>
.IP \(bu
Mercurial: hg+(http|https)://<hg path>
.IP \(bu
HTTP: http://<server>/<filename>
where <filename> is a (compressed) tar archive. For verification purposes, also
an
.BR md5sum (1)
generated hash must exist at the same location as <filename>.md5.
.TP
\fBLOGUSER\fP Account name on the install server to save log files and call
.BR fai-chboot (8).
At the end of an installation,
.BR fai (8)
may connect to the install server using
.BR FAI_LOGPROTO
(see below) to store the generated log files and to change the network boot
configuration of the target host.
To fully enable this, configure .rhosts and PAM such that the configured user
can log in from all install clients without password.
This account should have write permissions for /srv/tftp/fai. For example, you
can use write permissions for the group linuxadm. chgrp linuxadm
/srv/tftp/fai;chmod g+w /srv/tftp/fai.
If the variable is undefined, this feature is disabled.
.TP
\fBFAI_LOGPROTO\fP Protocol for saving logs
Supported values are: ssh, rsh, and ftp. If undefined use ssh. Will only be used
if
.BR LOGUSER
is set.
.TP
\fBFAI_DEBMIRROR\fP Access Debian mirror via NFS-mounted directory
If defined, install clients mount the NFS share to $MNTPOINT.
Syntax: <host>:<exported directory>
.SH SEE ALSO
.BR fai (8),
.BR fai\-make-nfsroot (8),
.BR fai\-setup (8),
.BR fai\-mirror (1),
.BR fai\-cd (8)
.br
This file is part of FAI (Fully Automatic Installation). See the FAI
manual for more information. The FAI homepage is http://fai-project.org.
.SH AUTHOR
This man page was written by Michael Tautschnig <mt@debian.org>.
|
