1davfs2.conf(5) 1.4.5 davfs2.conf(5)
2
6 davfs2.conf - Configuration file for mount.davfs
7
11 There is a system wide configuration file /etc/davfs2/davfs2.conf and
12 user configuration files ~/.davfs2/davfs2.conf. When mount.davfs is
13 invoked by root, only the system wide configuration file is read. When
14 invoked by an ordinary user, the user configuration file is read in
15 addition. Settings from the user configuration file will take prece‐
16 dence over the system wide configuration.
17 The configuration file consists of lines where each line contains a
20 keyword value pair. Keyword and value are seperated by spaces and/or
21 tabs.
22 The file may contain sections that are for one specific mount point
25 only. Such a section starts with a line, that contains the full path
26 of the mount point enclosed in square brackets. The section ends at the
27 start of the next section or the end of file. Options that shall apply
28 to all mounted file system must come before the first sections. Options
29 given in a mount specific section will have precedence.
30
34 kernel_fs coda
35 proxy foo.bar:8080
36 use_locks 0
37 [/media/dav]
38 use_locks 1
39 [/home/otto/mywebspace]
40 gui_optimize 1
41 All mounted davfs2 file systems will use the coda kernel file system
44 and the proxy foo.bar. All davfs2 file systems expect /media/dav will
45 disable the use of the locks. /home/otto/mywebspace will use the
46 gui_optimize option.
47
50 Lines that only contain spaces and tabs (empty lines) are ignored.
51 # indicates a comment. The rest of the line is ignored.
54 \ is the escape character.
57 "" is used for quotation.
60 If a value contains one of the special characters space, tab, #, \, or
63 ", this character must be escaped by a preceding \. Use ’\ ’ instead of
64 ’ ’, ’\#’ instead of ’#’, ’\\’ instead of ’\’ and ’\"’ instead of ’"’.
65 Values containing spaces, tabs or # may instead be enclosed in double
68 quotes. But " and ’ must be escaped even within double quotes. If the
69 starting line of a section is enclosed in double quotes, the square
70 brakets must be within the quotes (like "[/home/otto/with space]").
71 Boolean option values (yes/no) must be given as numerical value. 0 for
74 no, 1 for yes.
75
80 dav_user
81 When invoked by root the mount.davfs daemon will run as this
82 user. Value must be given as name, not as numerical id.
83 Default: davfs2
84 Only allowed in the system wide configuration file.
85 dav_group
88 The group of the running mount.davfs daemon. Ordinary users must
89 be member of this group in order to mount a davfs2 file system.
90 Value must be given as name, not as numerical id.
91 Default: davfs2
92 Only allowed in the system wide configuration file.
93 ignore_home
96 An ordinary user is not allowed to mount within the home direc‐
97 tory of another user. But sometimes system users (like nobody)
98 get assigned home directories (like /), that include common
99 mount points. This option allows to give a comma seperated list
100 of system users that will be excluded from this check.
101 Only allowed in the system wide configuration file.
102 kernel_fs
105 Which kernel file system to use, to integrate into the virtual
106 file system. Possible values are fuse and coda.
107 Default: fuse
108 buf_size
111 Size in KiByte of the buffer used to communicate with the kernel
112 file system. Only usefull with fuse, where read and write oper‐
113 ations may profit from a larger buffer.
114 Default: 16
115
119 use_proxy
120 Whether to use a proxy to connect to the WebDAV server. 0 = no,
121 1 = yes. If no proxy is defined in the configration file or the
122 environment variables https_proxy, http_proxy and all_proxy,
123 this option has no effect.
124 Default: 1
125 Only allowed in the system wide configuration file.
126 proxy Name of the proxy. The name must be the fully qualified domain
129 name (no scheme). If the proxy port differs from the default of
130 8080, it must be appended, seperated by a colon. Examples:
131 foo.bar:1704 or foo.bar
132 Only allowed in the system wide configuration file.
133 servercert
136 Name of a certificate file in PEM format. The name of the file
137 may be given as absolute path or as file name only. In the lat‐
138 ter case the directories ~/.davfs2/certs and /etc/davfs2/certs
139 will be searched.
140 This option is intended for self-signed server certificates.
141 Self-signed means issuer and subject are the same. Common name
142 (CN) must be the domain name of the server.
143 In case the server certificate is not self-singed, this file
144 must contain the certificate of the certificate authority (CA)
145 that signed the server certificate, not the the server certifi‐
146 cate itself. If an hirarchy of CA's is involved (the CA that
147 signed the server certificate is not the root CA), the file must
148 contain all the certificates from the chain of CAs involved,
149 beginning with the CA that signed the server certificate, up to
150 the self-signed certificate of the root CA. (The option name
151 servertcert is a misnomer in this case. Sorry.) You can create
152 the file by concatenating all the CA-certificates involved.
153 Note: Even if the certificate is trusted, that does not mean it
154 is accepted. There is the additional constraint, that the cer‐
155 tificate presented by the server must belong to the server. The
156 CN in the server certificate must be the domain name of the
157 server. There is currently no way to automatically accept cer‐
158 tificates that don't belong to the server.
159 clientcert
162 Name of a certificate in PKCS#12 format that will be used to
163 authenticate with the server. The name of the file may be given
164 as absolute path or as file name only. In the latter case the
165 directories ~/.davfs2/certs/private and /etc/davfs2/certs/pri‐
166 vate will be searched.
167 secrets
170 Name of a file that holds the credentials for servers and the
171 proxy, and passwords to decrypt the client certificate. The name
172 must be an absolute path. The file must be read and writable by
173 the owner only (mode 600).
174 Default: ~/.davfs2/secrets
175 Only allowed in the user configuration file. The system wide
176 secrets file is allways /etc/davfs2/secrets.
177 ask_auth
180 Ask the user interactively for credentials and passwords if not
181 found in the secretsfile. Ask the user if a servercert cannot be
182 verified. 0 = no, 1 = yes.
183 Default: 1
184 use_locks
187 Whether to lock files on the server when they are opened for
188 writing. 0 = no, 1 = yes.
189 Default: 1
190 lock_owner
193 A string send to the server to identify the owner of a lock. If
194 a WebDAV resource is used at the same time by different clients
195 using the same credentials, different values for lock_owner
196 should be choosen.
197 Default: the username from the credentials
198 lock_timeout
201 How long in seconds locks should be valid, before the server
202 removes them. The server may ignore this and set its own time‐
203 out value.
204 Default: 1800
205 lock_refresh
208 That many seconds before the lock times out, mount.davfs will
209 try to refresh the lock. The value should be substantially
210 greater than delay_upload.
211 Default: 60
212 use_expect100
215 To avoid uploading big files that will be refused by the
216 server, mount.davfs uses the header expect: 100-continue to get
217 the o.k. from the server before uploading. Not all servers
218 understand this. 0 = no, 1 = yes.
219 Default: 0
220 if_match_bug
223 Some servers do not handle If-Match and If-None-Match-headers
224 correctly. This otion tells mount.davfs to use HEAD instead of
225 thes headers. 0 = no, 1 = yes.
226 Default: 0
227 drop_weak_etags
230 Popular servers send a weak etag whenever they are not able to
231 calculate a strong one. This weak etag will never be valid, but
232 after one second it is silently turned into a strong, valid
233 etag. With this flag set to 1, mount.davfs will never use this
234 weak etags. If the flag is 0, the weakness indicator will be
235 removed and the etag is assumed to be strong. There is some dan‐
236 ger of the Lost-Update-Problem with this. But it is minimized
237 when using locks.
238 You should turn this on, when you can't use locks and there is
239 the danger of concurrent access to the same resource. In this
240 case the etag is not used at all and the resource cannot be
241 cached.
242 0 = no, 1 = yes.
243 Default: 0
244 allow_cookie
247 Some servers will only work when they are allowed to set a
248 cookie and this cookie is returned in subsequent requests. This
249 option adds very simple cookie support. It supports just one
250 cookie which should usually be a session ID. 0 = no, 1 = yes.
251 Default: 0
252 precheck
255 If option if_match_bug is set: use HEAD-requests to check for
256 existence or modification of a file to avoid unintended over‐
257 writing what somebody else changed. Has no effect if option
258 if_match_bug is 0. You should only set it 0, if there is no con‐
259 current access to the server. 0 = no, 1 = yes.
260 Default: 1
261 ignore_dav_header
264 Some servers send wrong information about their capabilities in
265 the DAV-header. In this case the header should be ignored.
266 Default: 0
267 server_charset
270 When extracting file names from the path component of the URL,
271 mount.davfs will assume they are encoded using this character
272 set and translate file names to the local character set. This is
273 not about encoding of file contents and not about HTTP escaping
274 rules.
275 There is no means in HTTP to know the character encoding of the
276 path component. There may be even different encodings within the
277 same path, as the encoding of file names is often defined by the
278 clients that created them. Nowadays it is best to use only
279 UTF-8 encoding and to do no conversion. If you are not sure that
280 all clients understand UTF-8, restrict file names to pure
281 us-ascii. Never use characters in file names, that may have a
282 special function on some operating systems (like /, : and \).
283 Default: no character set conversion
284 connect_timeout
287 When creating a TCP connection to the server mount.davfs will
288 wait that many seconds for an answer before assuming an error.
289 If a value of '0' is used then no explicit timeout handling is
290 set and the connect call will only timeout as dictated by the
291 TCP stack.
292 This parameter only takes effect if the version of neon in use
293 (neon version > 0.26) and the OS support non-blocking I/O.
294 Default: 10
295 read_timeout
298 How long in seconds mount.davfs will wait for an answer from the
299 server before assuming an error.
300 Default: 30
301 retry When mount.davfs can not reach the server it will try again
304 after retry seconds. For subsequent retries the interval will be
305 increased up to max_retry seconds.
306 Default: 30
307 max_retry
310 Maximum value of the retry interval.
311 Default: 300
312 max_upload_attempts
315 When uploading a changed file fails temporarily mount.davfs will
316 retry with increasing intervals, but not more often than this.
317 With a bad connection this will cause additional traffic. To
318 reduce traffic caused by unsuccessful attempts option
319 use_expect100 can be set. But please test it. Most proxies and
320 some servers don't support this header.
321 Default: 15
322 add_header
325 Your server might expect special headers to do what you want.
326 Different from other options, this one takes two values: the
327 name of the header and its value. Some ASP-backends to IIS seem
328 to require the Microsoft specific header "Translate: F". You can
329 add it like this:
330 add_header Translate F
331 mount.davfs will add header "Translate: F" on all requests.
332 This option is cumulative. You can enter more than one
333 add_header option and all of them will be added. Also add_header
334 options from /etc/davfs2/davfs2.conf and ~/.davfs2/davfs2.conf
335 are merged.
336
340 backup_dir
341 Each mounted davfs2 file system has a directory to store backups
342 of files that could not be stored back to the server. This sets
343 the name of this directory. You should regularly check this
344 directory.
345 Default: lost+found
346 cache_dir
349 The directory where mount.davfs will store cached files. For
350 every mount point a subdirectory will be created.
351 In the systemwide configuration file this will set the system
352 wide cache, used by root. In a users configuration file it will
353 set the cache used by this user.
354 Defaults: /var/cache/davfs2 and ~/.davfs2/cache
355 cache_size
358 The amount of disk space in MiByte that may be used. mount.davfs
359 will always take enough space to cache open files, ignoring this
360 value if necessary.
361 Default: 50
362 table_size
365 mount.davfs maintains a hash table with an entry for each known
366 file or directory. This gives the number of entries in this ta‐
367 ble. For large file systems (more than some hundreds of files)
368 increasing this number may speed up file operations. The value
369 should be a power of 2.
370 Default: 1024
371 dir_refresh
374 After mount.davfs has got information about files in a directory
375 it considers it valid for this time in seconds. Note: This does
376 not affect opening of files and reading a directory by an appli‐
377 cation.
378 Default: 60
379 file_refresh
382 When a file or directory is opened by an application,
383 mount.davfs will first check the server for a newer version. But
384 some applications do open calls on the same file in short
385 sequence. To avoid unecessary traffic mount.davfs will wait that
386 many seconds before it send a new request for the same informa‐
387 tion.
388 Default: 1
389 delay_upload
392 When a file that has been changed is closed, mount.davfs will
393 wait that many seconds before it will upload it to the server.
394 This will avoid uploading of temporary files that will be
395 removed immediately after closing. If you need the files to
396 appear on the server immediately after closing, set this option
397 to 0.
398 Default: 10
399 gui_optimize
402 When a file is opened, mount.davfs will have to check the server
403 whether there is a newer version. Graphical User Interfaces tend
404 to open just any file, slowing down things dramatically for
405 large directories. With this option mount.davfs will try to get
406 this information from all files in a directory with one PROPFIND
407 request. 0 = no, 1 = yes.
408 Default: 0
409
413 debug Send debug messages to the syslog daemon. The value tells what
414 kind of information shall be logged. The messages are send with
415 facility LOG_DAEMON and priority LOG_DEBUG. It depends from the
416 configuration of the syslog daemon where the messages will go
417 (propably /var/log/messages, /var/log/syslog or /var/log/dae‐
418 mon.log). Whether HTTP related debug messages are available
419 depends on your neon library.
420 Unlike other options, this option is cumulative. If there are
421 several debug entries with different values, all of them will be
422 applied. Also debug options from /etc/davfs2/davfs2.conf and
423 ~/.davfs2/davfs2.conf are merged.
424 Note: Debug messages let the log-files grow quickly. Never use
425 this option in normal operation of mount.davfs.
426 Default: no debugging messages
427 Recognized values:
429 config Command line and configuration options.
431 kernel Upcalls from the kernel file system.
433 cache Cache operations like adding and removing nodes.
435 http HTTP headers.
437 xml Parsing of the XML-body of WebDAV-requests.
439 httpauth
441 Negotiation of authentication.
442 locks Information about locks.
444 ssl TLS/SSL related stuff like certificates.
446 httpbody
448 Complete body of HTTP-responses.
449 secrets
451 Also print confidential information, which is usually
452 omitted or obscured.
453 most Includes config, kernel, cache and http.
455
459 This man page was written by by Werner Baumann <werner.baumann@online‐
460 home.de>.
461
465 http://savannah.nongnu.org/projects/davfs2
466
470 mount.davfs(8), umount.davfs(8), mount(8), umount(8), fstab(5)
471davfs2 2009-04-13 davfs2.conf(5)