first import

This commit is contained in:
wbaumann
2009-04-14 19:54:53 +00:00
commit d12d77382e
60 changed files with 28149 additions and 0 deletions

54
man/Makefile.am Normal file
View File

@ -0,0 +1,54 @@
## Makefile for man directory in davfs.
## Copyright (C) 2006, 2007, 2008, 2009 Werner Baumann
##
## This file is part of davfs2.
##
## davfs2 is free software; you can redistribute it and/or modify
## it under the terms of the GNU General Public License as published by
## the Free Software Foundation; either version 3 of the License, or
## (at your option) any later version.
##
## davfs2 is distributed in the hope that it will be useful,
## but WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
## GNU General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with davfs2; if not, write to the Free Software Foundation,
## Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. */
## Process this file with automake to produce Makefile.in
pkgsysconfdir = $(sysconfdir)/@PACKAGE@
pkglocalstatedir = $(dav_localstatedir)/mount.davfs
pkgsyscachedir = $(dav_syscachedir)/@PACKAGE@
mandir = $(datadir)/man
manual5dir = $(mandir)/man5
manual8dir = $(mandir)/man8
SUBDIRS = @dav_linguas@
DIST_SUBDIRS = de es
edit = sed \
-e 's|@PACKAGE[@]|$(PACKAGE)|g' \
-e 's|@PACKAGE_STRING[@]|$(PACKAGE_STRING)|g' \
-e 's|@PROGRAM_NAME[@]|mount.davfs|g' \
-e 's|@SYS_CONF_DIR[@]|$(pkgsysconfdir)|g' \
-e 's|@SYS_RUN[@]|$(pkglocalstatedir)|g' \
-e 's|@SYS_CACHE_DIR[@]|$(pkgsyscachedir)|g' \
-e 's|@SECRETSFILE[@]|secrets|g' \
-e 's|@CONFIGFILE[@]|$(PACKAGE).conf|g' \
-e 's|@CERTS_DIR[@]|certs|g' \
-e 's|@CLICERTS_DIR[@]|private|g' \
-e 's|@USER[@]|$(dav_user)|g' \
-e 's|@GROUP[@]|$(dav_group)|g'
manual5_DATA = davfs2.conf.5.gz
manual8_DATA = mount.davfs.8.gz umount.davfs.8.gz
EXTRA_DIST = davfs2.conf.5 mount.davfs.8 umount.davfs.8 \
davfs2.conf.5.pot mount.davfs.8.pot umount.davfs.8.pot \
po4a.conf template.translator
CLEANFILES = $(manual5_DATA) $(manual8_DATA)
%.gz: %
$(edit) $< | gzip -9 > $@

518
man/davfs2.conf.5 Normal file
View File

@ -0,0 +1,518 @@
.TH @CONFIGFILE@ 5 2009\-04\-13 @PACKAGE_STRING@
.SH NAME
\fB@CONFIGFILE@\fR \- Configuration file for \fB@PROGRAM_NAME@\fR
.SH DESCRIPTION
There is a system wide configuration file \fI@SYS_CONF_DIR@/@CONFIGFILE@\fR
and user configuration files \fI~/.@PACKAGE@/@CONFIGFILE@\fR. When
\fB@PROGRAM_NAME@\fR is invoked by root, only the system wide configuration
file is read. When invoked by an ordinary user, the user configuration file
is read in addition. Settings from the user configuration file will take
precedence over the system wide configuration.
.PP
The configuration file consists of lines where each line contains a keyword
value pair. Keyword and value are seperated by spaces and/or tabs.
.PP
The file may contain sections that are for one specific mount point only.
Such a section starts with a line, that contains the full path of the mount
point enclosed in square brackets. The section ends at the start of the next
section or the end of file. Options that shall apply to all mounted file
system must come before the first sections. Options given in a mount specific
section will have precedence.
.SH EXAMPLE
kernel_fs coda
.br
proxy foo.bar:8080
.br
use_locks 0
.br
.br
[/media/dav]
.br
use_locks 1
.br
.br
[/home/otto/mywebspace]
.br
gui_optimize 1
.PP
All mounted @PACKAGE@ file systems will use the coda kernel file system and the
proxy foo.bar. All @PACKAGE@ file systems expect /media/dav will disable the
use of the locks. /home/otto/mywebspace will use the gui_optimize option.
.SH GENERAL SYNTAX RULES
Lines that only contain spaces and tabs (empty lines) are ignored.
.PP
# indicates a comment. The rest of the line is ignored.
.PP
\(rs is the escape character.
.PP
\(dq" is used for quotation.
.PP
If a value contains one of the special characters space, tab, #, \(rs, or \(dq,
this character must be escaped by a preceding \(rs. Use \(cq\(rs\ \(cq instead
of \(cq\ \(cq, \(cq\(rs#\(cq instead of \(cq#\(cq, \(cq\(rs\(rs\(cq instead of
\(cq\(rs\(cq and \(cq\(rs\(dq\(cq instead of \(cq\(dq\(cq.
.PP
Values containing spaces, tabs or # may instead be enclosed in double quotes.
But \(dq and \(cq must be escaped even within double quotes. If the starting line
of a section is enclosed in double quotes, the square brakets must be within
the quotes (like \(dq[/home/otto/with space]\(dq).
.PP
Boolean option values (yes/no) must be given as numerical value.
0 for no, 1 for yes.
.SH AVAILABLE CONFIGURATION OPTIONS
.SH General Options
.TP
.B dav_user
When invoked by root the \fB@PROGRAM_NAME@\fR daemon will run as this user.
Value must be given as \fIname\fP, \fBnot\fR as numerical id.
.br
Default: @USER@
.br
\fBOnly allowed in the system wide configuration file.\fR
.TP
.B dav_group
The group of the running \fB@PROGRAM_NAME@\fR daemon. Ordinary users must
be member of this group in order to mount a @PACKAGE@ file system.
Value must be given as \fIname\fP, \fBnot\fR as numerical id.
.br
Default: @GROUP@
.br
\fBOnly allowed in the system wide configuration file.\fR
.TP
.B ignore_home
An ordinary user is not allowed to mount within the home directory of another
user. But sometimes system users (like \fInobody\fP) get assigned home
directories (like /), that include common mount points. This option allows to
give a comma seperated list of system users that will be excluded from this
check.
.br
\fBOnly allowed in the system wide configuration file.\fR
.TP
.B kernel_fs
Which kernel file system to use, to integrate into the virtual file system.
Possible values are \fIfuse\fP and \fIcoda\fP.
.br
Default: fuse
.TP
.B buf_size
Size in KiByte of the buffer used to communicate with the kernel file system.
Only usefull with \fIfuse\fP, where read and write operations may profit
from a larger buffer.
.br
Default: 16
.SH WebDAV Related Options
.TP
.B use_proxy
Whether to use a proxy to connect to the WebDAV server. 0 = no, 1 = yes.
If no proxy is defined in the configration file or the environment variables
\fBhttps_proxy\fR, \fBhttp_proxy\fR and \fBall_proxy\fR, this option has no
effect.
.br
Default: 1
.br
\fBOnly allowed in the system wide configuration file.\fR
.TP
.B proxy
Name of the proxy. The name must be the fully qualified domain name
(no scheme). If the proxy port differs from the default of 8080, it
must be appended, seperated by a colon. Examples: \fIfoo.bar:1704\fP or
\fIfoo.bar\fP
.br
\fBOnly allowed in the system wide configuration file.\fR
.TP
.B servercert
Name of a certificate file in PEM format. The name of the file may be
given as absolute path or as file name only. In the latter case the
directories \fI~/.@PACKAGE@/@CERTS_DIR@\fP and
\fI@SYS_CONF_DIR@/@CERTS_DIR@\fP will be searched.
.br
This option is intended for self-signed server certificates. Self-signed
means issuer and subject are the same. Common name (CN) must be the
domain name of the server.
.br
In case the server certificate is not self-singed, this file must contain
the certificate of the certificate authority (CA) that signed the server
certificate, not the the server certificate itself. If an hirarchy of
CA's is involved (the CA that signed the server certificate is not the
root CA), the file must contain all the certificates from the chain of
CAs involved, beginning with the CA that signed the server certificate,
up to the self-signed certificate of the root CA. (The option name
\fBservertcert\fR is a misnomer in this case. Sorry.) You can create the
file by concatenating all the CA-certificates involved.
.br
\fBNote:\fR Even if the certificate is trusted, that does not mean it
is accepted. There is the additional constraint, that the certificate
presented by the server must belong to the server. The CN in the
server certificate must be the domain name of the server. There is
currently no way to automatically accept certificates that don't
belong to the server.
.TP
.B clientcert
Name of a certificate in PKCS#12 format that will be used to authenticate
with the server. The name of the file may be given as absolute path or as
file name only. In the latter case the directories
\fI~/.@PACKAGE@/@CERTS_DIR@/@CLICERTS_DIR@\fP and
\fI@SYS_CONF_DIR@/@CERTS_DIR@/@CLICERTS_DIR@\fP will be searched.
.TP
.B secrets
Name of a file that holds the credentials for servers and the proxy, and
passwords to decrypt the client certificate. The name must be an absolute
path. The file must be read and writable by the owner only (mode 600).
.br
Default: ~/.@PACKAGE@/@SECRETSFILE@
.br
\fBOnly allowed in the user configuration file.\fR The system wide
secrets file is allways \fI@SYS_CONF_DIR@/@SECRETSFILE@\fP.
.TP
.B ask_auth
Ask the user interactively for credentials and passwords if not found in the
secretsfile. 0 = no, 1 = yes.
.br
Default: 1
.TP
.B use_locks
Whether to lock files on the server when they are opened for writing.
0 = no, 1 = yes.
.br
Default: 1
.TP
.B lock_owner
A string send to the server to identify the owner of a lock. If a WebDAV
resource is used at the same time by different clients using the same
credentials, different values for lock_owner should be choosen.
.br
Default: the username from the credentials
.TP
.B lock_timeout
How long in seconds locks should be valid, before the server removes them.
The server may ignore this and set its own timeout value.
.br
Default: 1800
.TP
.B lock_refresh
That many seconds before the lock times out, \fB@PROGRAM_NAME@\fR will try to
refresh the lock. The value should be substantially greater than
\fBdelay_upload\fR.
.br
Default: 60
.TP
.B use_expect100
To avoid uploading big files that will be refused by the server,
\fB@PROGRAM_NAME@\fR uses the header \fIexpect: 100\-continue\fP to get the o.k.
from the server before uploading. Not all servers understand this.
0 = no, 1 = yes.
.br
Default: 0
.TP
.B if_match_bug
Some servers do not handle If-Match and If-None-Match-headers correctly.
This otion tells \fB@PROGRAM_NAME@\fR to use HEAD instead of thes headers.
0 = no, 1 = yes.
.br
Default: 0
.TP
.B drop_weak_etags
Popular servers send a weak etag whenever they are not able to calculate
a strong one. This weak etag will never be valid, but after one second it
is silently turned into a strong, valid etag. With this flag set to 1,
\fB@PROGRAM_NAME@\fR will never use this weak etags. If the flas is 0,
the weakness indicator will be removed and the etag is assumed to be
strong. There is some danger of the Lost-Update-Problem with
this. But it is minimized when using locks.
.br
You should turn this on, when you can't use locks and there is the
danger of concurrent access to the same resource. In this case the
etag is not used at all and the resource cannot be cached.
.br
0 = no, 1 = yes.
.br
Default: 0
.TP
.B allow_cookie
Some servers will only work when they are allowed to set a cookie and this
cookie is returned in subsequent requests. This option adds very simple
cookie support. It supports just one cookie which should usually be
a session ID.
0 = no, 1 = yes.
.br
Default: 0
.TP
.B precheck
If option \fBif_match_bug\fR is set: use HEAD-requests to check for existence
or modification of a file to avoid unintended overwriting what somebody
else changed. Has no effect if option \fBif_match_bug\fR is 0. You should only
set it 0, if there is no concurrent access to the server.
0 = no, 1 = yes.
.br
Default: 1
.TP
.B ignore_dav_header
Some servers send wrong information about their capabilities in the DAV-header.
In this case the header should be ignored.
.br
Default: 0
.TP
.B server_charset
When extracting file names from the path component of the URL,
\fB@PROGRAM_NAME@\fR will assume they are encoded using this character set
and translate file names to the local character set. This is \fBnot\fR
about encoding of file contents and \fBnot\fR about HTTP escaping rules.
.br
There is no means in HTTP to know the character encoding of the path
component. There may be even different encodings within the same path, as
the encoding of file names is often defined by the clients that created them.
Nowadays it is best to use only UTF\-8 encoding and to do no conversion. If
you are not sure that all clients understand UTF\-8, restrict file names to
pure us\-ascii. Never use characters in file names, that may have a special
function on some operating systems (like /, : and \(rs).
.br
Default: no character set conversion
.TP
.B connect_timeout
When creating a TCP connection to the server \fB@PROGRAM_NAME@\fR will
wait that many seconds for an answer before assuming an error. If a value
of '0' is used then no explicit timeout handling is set and the connect call
will only timeout as dictated by the TCP stack.
.br
This parameter only takes effect if the version of neon in use
(neon version > 0.26) and the OS support non-blocking I/O.
.br
Default: 10
.TP
.B read_timeout
How long in seconds \fB@PROGRAM_NAME@\fR will wait for an answer from the
server before assuming an error.
.br
Default: 30
.TP
.B retry
When \fB@PROGRAM_NAME@\fR can not reach the server it will try again after
\fBretry\fR seconds. For subsequent retries the interval will be increased
up to \fBmax_retry\fR seconds.
.br
Default: 30
.TP
.B max_retry
Maximum value of the retry interval.
.br
Default: 300
.TP
.B add_header
Your server might expect special headers to do what you want. Different from
other options, this one takes two values: the name of the header and its value.
Example:
.br
add_header Translate F
.br
\fB@PROGRAM_NAME@\fR will add header "Translate: F" on all requests.
.br
This option is cumulative. You can enter more than one add_header option
and all of them will be added. Also add_header options from
@SYS_CONF_DIR@/@CONFIGFILE@ and ~/.@PACKAGE@/@CONFIGFILE@ are merged.
.SH Cache Related Options
.TP
.B backup_dir
Each mounted @PACKAGE@ file system has a directory to store backups of files
that could not be stored back to the server. This sets the name of this
directory. You should regularly check this directory.
.br
Default: lost+found
.TP
.B cache_dir
The directory where \fB@PROGRAM_NAME@\fR will store cached files. For every
mount point a subdirectory will be created.
.br
In the systemwide configuration file this will set the system wide cache,
used by root. In a users configuration file it will set the cache used by
this user.
.br
Defaults: @SYS_CACHE_DIR@ and ~/.@PACKAGE@/cache
.TP
.B cache_size
The amount of disk space in MiByte that may be used. \fB@PROGRAM_NAME@\fR
will always take enough space to cache open files, ignoring this value if
necessary.
.br
Default: 50
.TP
.B table_size
\fB@PROGRAM_NAME@\fR maintains a hash table with an entry for each known file
or directory. This gives the number of entries in this table. For large
file systems (more than some hundreds of files) increasing this number may
speed up file operations. The value should be a power of 2.
.br
Default: 1024
.TP
.B dir_refresh
After \fB@PROGRAM_NAME@\fR has got information about files in a directory it
considers it valid for this time in seconds. Note: This does not affect
opening of files and reading a directory by an application.
.br
Default: 60
.TP
.B file_refresh
When a file or directory is opened by an application, \fB@PROGRAM_NAME@\fR
will first check the server for a newer version. But some applications do
open calls on the same file in short sequence. To avoid unecessary traffic
\fB@PROGRAM_NAME@\fR will wait that many seconds before it send a new request
for the same information.
.br
Default: 1
.TP
.B delay_upload
When a file that has been changed is closed, \fB@PROGRAM_NAME@\fR will wait
that many seconds before it will upload it to the server. This will avoid
uploading of temporary files that will be removed immediately after closing.
If you need the files to appear on the server immediately after closing,
set this option to 0.
.br
Default: 10
.TP
.B gui_optimize
When a file is opened, \fB@PROGRAM_NAME@\fR will have to check the server
whether there is a newer version. Graphical User Interfaces tend to open
just any file, slowing down things dramatically for large directories.
With this option \fB@PROGRAM_NAME@\fR will try to get this information
from all files in a directory with one PROPFIND request. 0 = no, 1 = yes.
.br
Default: 0
.SH Debugging Options
.TP
.B debug
Send debug messages to the syslog daemon. The value tells what kind of
information shall be logged. The messages are send with facility LOG_DAEMON
and priority LOG_DEBUG. It depends from the configuration of the syslog daemon
where the messages will go (propably /var/log/messages, /var/log/syslog or
/var/log/daemon.log). Whether HTTP related debug messages are available
depends on your neon library.
.br
Unlike other options, this option is cumulative. If there are several debug
entries with different values, all of them will be applied. Also debug options
from @SYS_CONF_DIR@/@CONFIGFILE@ and ~/.@PACKAGE@/@CONFIGFILE@ are merged.
.br
\fBNote:\fR Debug messages let the log-files grow quickly. Never use this
option in normal operation of mount.davfs.
.br
Default: no debugging messages
.RS
.TP
.B Recognized values:
.TP
.B config
Command line and configuration options.
.TP
.B kernel
Upcalls from the kernel file system.
.TP
.B cache
Cache operations like adding and removing nodes.
.TP
.B http
HTTP headers.
.TP
.B xml
Parsing of the XML-body of WebDAV-requests.
.TP
.B httpauth
Negotiation of authentication.
.TP
.B locks
Information about locks.
.TP
.B ssl
TLS/SSL related stuff like certificates.
.TP
.B httpbody
Complete body of HTTP-responses.
.TP
.B secrets
Also print confidential information, which is usually omitted or obscured.
.TP
.B most
Includes config, kernel, cache and http.
.RE
.SH AUTHORS
This man page was written by by Werner Baumann
<werner.baumann@onlinehome.de>.
.SH DAVFS2 HOME
http://savannah.nongnu.org/projects/davfs2
.SH SEE ALSO
.BR @PROGRAM_NAME@ (8),
.BR u@PROGRAM_NAME@ (8),
.BR mount (8),
.BR umount (8),
.BR fstab (5)

1103
man/davfs2.conf.5.pot Normal file

File diff suppressed because it is too large Load Diff

53
man/de/Makefile.am Normal file
View File

@ -0,0 +1,53 @@
## Makefile for man/de directory in davfs.
## Copyright (C) 2006, 2007, 2008, 2009 Werner Baumann
##
## This file is part of davfs2.
##
## davfs2 is free software; you can redistribute it and/or modify
## it under the terms of the GNU General Public License as published by
## the Free Software Foundation; either version 3 of the License, or
## (at your option) any later version.
##
## davfs2 is distributed in the hope that it will be useful,
## but WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
## GNU General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with davfs2; if not, write to the Free Software Foundation,
## Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. */
## Process this file with automake to produce Makefile.in
pkgsysconfdir = $(sysconfdir)/@PACKAGE@
pkglocalstatedir = $(dav_localstatedir)/mount.davfs
pkgsyscachedir = $(dav_syscachedir)/@PACKAGE@
mandir = $(datadir)/man
manual5dir = $(mandir)/de/man5
manual8dir = $(mandir)/de/man8
edit = sed \
-e 's|@PACKAGE[@]|$(PACKAGE)|g' \
-e 's|@PACKAGE_STRING[@]|$(PACKAGE_STRING)|g' \
-e 's|@PROGRAM_NAME[@]|mount.davfs|g' \
-e 's|@SYS_CONF_DIR[@]|$(pkgsysconfdir)|g' \
-e 's|@SYS_RUN[@]|$(pkglocalstatedir)|g' \
-e 's|@SYS_CACHE_DIR[@]|$(pkgsyscachedir)|g' \
-e 's|@SECRETSFILE[@]|secrets|g' \
-e 's|@CONFIGFILE[@]|$(PACKAGE).conf|g' \
-e 's|@CERTS_DIR[@]|certs|g' \
-e 's|@CLICERTS_DIR[@]|private|g' \
-e 's|@USER[@]|$(dav_user)|g' \
-e 's|@GROUP[@]|$(dav_group)|g'
manual5_DATA = davfs2.conf.5.gz
manual8_DATA = mount.davfs.8.gz umount.davfs.8.gz
EXTRA_DIST = davfs2.conf.5 mount.davfs.8 umount.davfs.8 \
davfs2.conf.5.po mount.davfs.8.po umount.davfs.8.po \
davfs2.conf.5.translator mount.davfs.8.translator \
umount.davfs.8.translator
CLEANFILES = $(manual5_DATA) $(manual8_DATA)
%.gz: %
$(edit) $< | gzip -9 > $@

1326
man/de/davfs2.conf.5.po Normal file

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,4 @@
PO4A-HEADER:mode=after;position=^\.SH AUTOREN;beginboundary=^\.SH
.SH ÜBERSETZER
Das Handbuch wurde von Werner Baumann <werner.baumann@onlinehome.de>
übersetzt. 2008-01-02

1322
man/de/mount.davfs.8.po Normal file

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,4 @@
PO4A-HEADER:mode=after;position=^\.SH AUTOREN;beginboundary=^\.SH
.SH ÜBERSETZER
Das Handbuch wurde von Werner Baumann <werner.baumann@onlinehome.de>
übersetzt. 2008-01-02

249
man/de/umount.davfs.8.po Normal file
View File

@ -0,0 +1,249 @@
# #-#-#-#-# umount.davfs.8.po (davfs2 1.4.0) #-#-#-#-#
# German translation of umount.davfs(8) man page.
# Copyright (C) 2007 Werner Baumann
# Werner Baumann <werner.baumann@onlinehome.de>, 2007.
#
msgid ""
msgstr ""
"Project-Id-Version: davfs2 1.4.0\n"
"POT-Creation-Date: 2009-04-13 21:30+0300\n"
"PO-Revision-Date: 2009-04-13 21:49+0200\n"
"Last-Translator: Werner Baumann <werner.baumann@onlinehome.de>\n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
# type: TH
#: davfs2.conf.5:1 mount.davfs.8:1 umount.davfs.8:1
#, no-wrap
msgid "2009-04-13"
msgstr "2009-04-13"
# type: TH
#: davfs2.conf.5:1 mount.davfs.8:1 umount.davfs.8:1
#, no-wrap
msgid "@PACKAGE_STRING@"
msgstr "@PACKAGE_STRING@"
# type: SH
#: davfs2.conf.5:4 mount.davfs.8:3 umount.davfs.8:3
#, no-wrap
msgid "NAME"
msgstr "BEZEICHNUNG"
# type: SH
#: davfs2.conf.5:9 mount.davfs.8:22 umount.davfs.8:20
#, no-wrap
msgid "DESCRIPTION"
msgstr "BESCHREIBUNG"
# type: SH
#: davfs2.conf.5:501 mount.davfs.8:514 umount.davfs.8:79
#, no-wrap
msgid "AUTHORS"
msgstr "AUTOREN"
# type: SH
#: davfs2.conf.5:507 mount.davfs.8:531 umount.davfs.8:84
#, no-wrap
msgid "DAVFS2 HOME"
msgstr "DAVFS2 HOME"
# type: Plain text
#: davfs2.conf.5:510 mount.davfs.8:534 umount.davfs.8:87
msgid "http://savannah.nongnu.org/projects/davfs2"
msgstr "http://savannah.nongnu.org/projects/davfs2"
# type: SH
#: davfs2.conf.5:512 mount.davfs.8:536 umount.davfs.8:89
#, no-wrap
msgid "SEE ALSO"
msgstr "SIEHE AUCH"
# type: SH
#: mount.davfs.8:8 umount.davfs.8:8
#, no-wrap
msgid "SYNOPSIS"
msgstr "ÜBERSICHT"
# type: SH
#: mount.davfs.8:15 umount.davfs.8:15
#, no-wrap
msgid "SYNOPSIS (root only)"
msgstr "ÜBERSICHT (nur für root)"
# type: Plain text
#: mount.davfs.8:61 umount.davfs.8:30
msgid ""
"I<dir> is the mountpoint where the WebDAV resource is mounted on. It may be "
"an absolute or relative path."
msgstr ""
"I<dir> ist der Einhängepunkt. Es kann eine absolute oder relative Pfadangabe "
"sein."
# type: SH
#: mount.davfs.8:68 umount.davfs.8:51
#, no-wrap
msgid "OPTIONS"
msgstr "OPTIONEN"
# type: TP
#: mount.davfs.8:70 umount.davfs.8:53
#, no-wrap
msgid "B<-V --version>"
msgstr "B<-V --version>"
# type: Plain text
#: mount.davfs.8:73 umount.davfs.8:56
msgid "Output version."
msgstr "Zeige die Version an."
# type: TP
#: mount.davfs.8:74 umount.davfs.8:57
#, no-wrap
msgid "B<-h --help>"
msgstr "B<-h --help>"
# type: Plain text
#: mount.davfs.8:77 umount.davfs.8:60
msgid "Print a help message."
msgstr "Zeige einen Hilfe-Text an."
# type: SH
#: mount.davfs.8:345 umount.davfs.8:67
#, no-wrap
msgid "FILES"
msgstr "DATEIEN"
# type: TP
#: mount.davfs.8:406 umount.davfs.8:69
#, no-wrap
msgid "I<@SYS_RUN@>"
msgstr "I<@SYS_RUN@>"
# type: SH
#: mount.davfs.8:509 umount.davfs.8:74
#, no-wrap
msgid "BUGS"
msgstr "FEHLER"
# type: TH
#: umount.davfs.8:1
#, no-wrap
msgid "u@PROGRAM_NAME@"
msgstr "u@PROGRAM_NAME@"
# type: Plain text
#: umount.davfs.8:6
msgid "u@PROGRAM_NAME@ - Umount-helper to unmount a @PACKAGE@ file system"
msgstr "u@PROGRAM_NAME@ - Umount-Hilfsprogramm für @PACKAGE@ Dateisysteme"
# type: Plain text
#: umount.davfs.8:11
msgid "B<u@PROGRAM_NAME@ [-h | --help] [-V | --version]>"
msgstr "B<u@PROGRAM_NAME@ [-h | --help] [-V | --version]>"
# type: Plain text
#: umount.davfs.8:13
msgid "B<umount >I<dir>"
msgstr "B<umount >I<dir>"
# type: Plain text
#: umount.davfs.8:18
msgid "B<u@PROGRAM_NAME@ >I<dir>"
msgstr "B<u@PROGRAM_NAME@ >I<dir>"
# type: Plain text
#: umount.davfs.8:26
msgid ""
"B<u@PROGRAM_NAME@> is a umount helper program. It is called by the B<umount>"
"(8) command. Its purpose is to prevent the umount command from returning "
"unless B<@PROGRAM_NAME@> has synchronized all its cached files with the "
"webdav server."
msgstr ""
"B<u@PROGRAM_NAME@> ist ein Hilfsprogramm, das von B<umount>(8) aufgerufen "
"wird. Es soll verhindern, dass das umount-Kommando zurück kehrt, bevor "
"B<@PROGRAM_NAME@> alle geänderten Dateien aus dem Cache auf den WebDAV-"
"Server zurück sichern konnte."
# type: Plain text
#: umount.davfs.8:39
msgid ""
"While for local file systems B<umount>(8) will only return when all cached "
"data have been written to disk, this is not automatically true for a mounted "
"B<@PACKAGE@> file system. With this umount helper the user can rely on the "
"familiar behaviour of B<umount>(8). To inform the operating system that the "
"file system uses a network connection, you should always use the B<_netdev> "
"option, when mounting as B<@PACKAGE@> file system."
msgstr ""
"Bei lokalen Dateisystemen kehrt B<umount>(8) erst zurück, wenn alle Daten "
"aus dem Cache auf die Festplatte geschrieben sind. Dies funkioniert bei "
"einem B<@PACKAGE@>-Dateisystem nicht automatisch. Mit diesem Hilfsprogramm "
"kann sich der Benutzer auf das bekannte Verhalten von B<umount>(8) "
"verlassen. Es sollte auch immer mit der Option B<_netdev> eingehängt werden, "
"damit das Betriebssystem darüber informiert wird, dass das B<@PACKAGE@>-"
"Dateisystem eine Netzwerkverbindung braucht."
# type: Plain text
#: umount.davfs.8:43
msgid ""
"Depending on the amount of data and the quality of the connection, "
"unmounting a B<@PACKAGE@> file system may take some seconds up to some hours."
msgstr ""
"Abhängig von der Datenmenge und der Qualität der Netzwerkverbindung kann das "
"Aushängen ein paar Sekunden, aber auch einige Stunden dauern."
# type: Plain text
#: umount.davfs.8:49
msgid ""
"If the B<@PROGRAM_NAME@> daemon encountered serious errors, "
"B<u@PROGRAM_NAME@> may return an error instead of unmounting the file "
"system. In this case try B<umount -i>. The B<-i> option will prevent "
"B<umount>(8) from calling B<u@PROGRAM_NAME@>."
msgstr ""
"Wenn der B<@PROGRAM_NAME@>-Hintergrundprozess ernste Probleme hat, kann "
"B<u@PROGRAM_NAME@> möglicherweise das Dateisystem nicht aushängen, sondern "
"meldet einen Fehler. Versuche es in diesem Fall mit B<umount -i>. Die Option "
"B<-i> hindert B<umount>(8) daran, B<u@PROGRAM_NAME@> aufzurufen."
# type: TP
#: umount.davfs.8:61
#, no-wrap
msgid "B<-f -l -n -r -v>"
msgstr "B<-f -l -n -r -v>"
# type: Plain text
#: umount.davfs.8:65
msgid ""
"This options are B<ignored>. They are only recognized for compatibility with "
"B<umount>(8)."
msgstr ""
"Dies Optionen dienen nur der Kompatibilität mit B<umount>(8) und werden "
"ignoriert."
# type: Plain text
#: umount.davfs.8:72
msgid "PID-files of running B<u@PROGRAM_NAME@> processes are looked up here."
msgstr ""
"Die PID-Dateien der laufenden B<@PROGRAM_NAME@>-Hintergrundprozesse werden "
"in diesem Verzeichnis gesucht."
# type: Plain text
#: umount.davfs.8:77
msgid "No known bugs."
msgstr "Derzeit keine bekannten."
# type: Plain text
#: umount.davfs.8:82
msgid ""
"This man page was written by Werner Baumann E<lt>werner.baumann@onlinehome."
"deE<gt>."
msgstr ""
"Diese Handbuch hat Werner Baumann E<lt>werner.baumann@onlinehome.deE<gt> "
"geschrieben."
# type: Plain text
#: umount.davfs.8:94
msgid "B<@PROGRAM_NAME@>(8), B<umount>(8), B<@CONFIGFILE@>(5), B<fstab>(5)"
msgstr "B<@PROGRAM_NAME@>(8), B<umount>(8), B<@CONFIGFILE@>(5), B<fstab>(5)"

View File

@ -0,0 +1,4 @@
PO4A-HEADER:mode=after;position=^\.SH AUTOREN;beginboundary=^\.SH
.SH ÜBERSETZER
Das Handbuch wurde von Werner Baumann <werner.baumann@onlinehome.de>
übersetzt. 2008-01-02

54
man/es/Makefile.am Normal file
View File

@ -0,0 +1,54 @@
## Makefile for man/es directory in davfs.
## Copyright (C) 2006, 2007, 2008, 2009 Werner Baumann
##
## This file is part of davfs2.
##
## davfs2 is free software; you can redistribute it and/or modify
## it under the terms of the GNU General Public License as published by
## the Free Software Foundation; either version 3 of the License, or
## (at your option) any later version.
##
## davfs2 is distributed in the hope that it will be useful,
## but WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
## GNU General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with davfs2; if not, write to the Free Software Foundation,
## Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. */
## Process this file with automake to produce Makefile.in
pkgsysconfdir = $(sysconfdir)/@PACKAGE@
pkglocalstatedir = $(dav_localstatedir)/mount.davfs
pkgsyscachedir = $(dav_syscachedir)/@PACKAGE@
mandir = $(datadir)/man
manual5dir = $(mandir)/es/man5
#manual8dir = $(mandir)/es/man8
edit = sed \
-e 's|@PACKAGE[@]|$(PACKAGE)|g' \
-e 's|@PACKAGE_STRING[@]|$(PACKAGE_STRING)|g' \
-e 's|@PROGRAM_NAME[@]|mount.davfs|g' \
-e 's|@SYS_CONF_DIR[@]|$(pkgsysconfdir)|g' \
-e 's|@SYS_RUN[@]|$(pkglocalstatedir)|g' \
-e 's|@SYS_CACHE_DIR[@]|$(pkgsyscachedir)|g' \
-e 's|@SECRETSFILE[@]|secrets|g' \
-e 's|@CONFIGFILE[@]|$(PACKAGE).conf|g' \
-e 's|@CERTS_DIR[@]|certs|g' \
-e 's|@CLICERTS_DIR[@]|private|g' \
-e 's|@USER[@]|$(dav_user)|g' \
-e 's|@GROUP[@]|$(dav_group)|g'
manual5_DATA = davfs2.conf.5.gz
#manual8_DATA = mount.davfs.8.gz umount.davfs.8.gz
#EXTRA_DIST = davfs2.conf.5 mount.davfs.8 umount.davfs.8 \
# davfs2.conf.5.po mount.davfs.8.po umount.davfs.8.po \
# davfs2.conf.5.translator mount.davfs.8.translator \
# umount.davfs.8.translator
EXTRA_DIST = davfs2.conf.5 davfs2.conf.5.po
CLEANFILES = $(manual5_DATA) $(manual8_DATA)
%.gz: %
$(edit) $< | gzip -9 > $@

1255
man/es/davfs2.conf.5.po Normal file

File diff suppressed because it is too large Load Diff

542
man/mount.davfs.8 Normal file
View File

@ -0,0 +1,542 @@
.TH @PROGRAM_NAME@ 8 "2009\-04\-13" @PACKAGE_STRING@
.SH NAME
@PROGRAM_NAME@ \- Mount a WebDAV resource in a directory
.SH SYNOPSIS
.B @PROGRAM_NAME@ [\-h | \-\-help] [\-V | \-\-version]
.br
.BI "mount {" dir " | " webdavserver }
.SH SYNOPSIS (root only)
.BI "mount \-t davfs [\-o " option [,...]] " webdavserver dir"
.br
.BI "@PROGRAM_NAME@ [\-o " option [,...]] " webdavserver dir"
.SH DESCRIPTION
\fB@PROGRAM_NAME@\fR allows you to mount the WebDAV resource identified by
.I webdavserver
into the local filesystem at
.I dir.
WebDAV is an extension to HTTP that allows remote, collaborative authoring
of Web resources, defined in RFC 4918.
\fB@PROGRAM_NAME@\fR is part of \fB@PACKAGE@\fR.
.PP
\fB@PACKAGE@\fR allows documents on a remote Web server to be edited using
standard applications. For example, a remote Web site could be updated
in\-place using the same development tools that initially created the site.
Or you may use a WebDAV resource for documents you want to access and edited
from different locations.
.PP
\fB@PACKAGE@\fR supports \fBTLS/SSL\fR (if the neon library supports it) and
proxies. \fB@PROGRAM_NAME@\fR runs as a daemon in userspace. It integrates into the
virtual file system by either the coda or the fuse kernel files system.
Currently CODA_KERNEL_VERSION 3 and FUSE_KERNEL_VERSION 7 are supported.
.PP
\fB@PROGRAM_NAME@\fR is usually invoked by the \fBmount\fR(8) command when
using the \fI\-t davfs\fP option. After mounting it runs as a daemon. To unmount
the \fBumount\fR(8) command is used.
.PP
\fIwebdavserver\fP must be a complete url, including scheme, fully qualified
domain name and path. Scheme may be \fBhttp\fR or \fBhttps\fR. If the path
contains spaces or other characters, that might be interpreted by the shell,
the url must be enclosed in double quotes
(e.g. \fI"http://foo.bar/name with spaces"\fP). See \fBURLS AND MOUNT POINTS
WITH SPACES\fR.
.PP
\fIdir\fP is the mountpoint where the WebDAV resource is mounted on.
It may be an absolute or relative path.
.PP
\fIfstab\fP may be used to define mounts and mount options as usual. In
place of the device the url of the WebDAV server must be given. There must not
be more than one entry in \fIfstab\fP for every mountpoint.
.SH OPTIONS
.TP
.B \-V \-\-version
Output version.
.TP
.B \-h \-\-help
Print a help message.
.TP
.B \-o
A comma\-separated list defines mount options to be used. Available options
are:
.RS
.TP
.B [no]auto
Can (not) be mounted with \fBmount \-a\fR.
.br
Default: \fBauto\fR.
.TP
.B conf=\fIabsolute path\fP
An alternative user configuration file. This option is intended for cases
where the default user configuration file in the users home directory can not
be used.
.br
Default: \fI~/.@PACKAGE@/@CONFIGFILE@\fP
.TP
.B [no]dev
(Do not) interpret character or block special devices on the file system.
This option is only included for compatibility with the \fBmount\fR(8)
program. It will allways be set to \fBnodev\fR
.TP
.B dir_mode=\fImode\fP
The default mode bits for directories in the mounted file system. Value given
in octal. s\-bits for user and group are allways silently ignored.
.br
Default: calculated from the umask of the mounting user; an x\-bit is
associated to every r\-bit in u\-g\-o.
.TP
.B [no]exec
(Do not) allow execution of any binaries on the mounted file system.
.br
Default: \fBexec\fR. (When mounting as an ordinary user, the \fBmount\fR(8)
program will set the default to \fBnoexec\fR.)
.TP
.B file_mode=\fImode\fP
The default mode bits for files in the mounted file system. Value given
in octal. s\-bits for user and group are allways silently ignored.
.br
Default: calculated from the umask of the mounting user; no x\-bits
are set for files.
.TP
.B gid=\fIgroup\fP
The group the mounted file system belongs to. It may be a numeric ID or a
group name. The mounting user, if not root, must be member of this group.
.br
Default: the primary group of the mounting user.
.TP
.B [no]_netdev
The file system needs a (no) network connection for operation. This information
allows the operating system to handle the file system properly at system start
and when the network is shut down.
.br
Default: \fB_netdev\fR
.TP
.B ro
Mount the file system read\-only.
.br
Default: \fBrw\fR.
.TP
.B rw
Mount the file system read\-write.
.br
Default: \fBrw\fR.
.TP
.B [no]suid
Do not allow set\-user\-identifier or set\-group\-identifier bits to take effect.
This option is only included for compatibility with the mount program. It will
allways be set to \fBnosuid\fR.
.TP
.B [no]user
(Do not) allow an ordinary user to mount the file system. The name of the
mounting user is written to \fImtab\fP so that he can unmount the file system
again. Option \fBuser\fR implies the options \fBnoexec\fR, \fBnosuid\fR and
\fBnodev\fR (unless overridden by subsequent options). This option makes only
sense when set in \fIfstab\fP.
.br
Default: ordinary users are not allowed to mount.
.TP
.B uid=\fIuser\fP
The owner of the mounted file system. It may be a numeric ID or a user name.
Only when mounted by root, this may be different from the mounting user.
.br
Default: ID of the mounting user.
.RE
.SH SECURITY POLICY
\fB@PROGRAM_NAME@\fR needs root privileges for mounting. But running a daemon,
that is connected to the internet, with root privileges is a security risk. So
\fB@PROGRAM_NAME@\fR will change its uid and gid when entering daemon mode.
.RS
.PP
When invoked by root \fB@PROGRAM_NAME@\fR will run as user \fB@USER@\fR and
group \fB@GROUP@\fR. This may be changed in \fI@SYS_CONF_DIR@/@CONFIGFILE@\fP.
.PP
When invoked by an ordinary user it will run with the id of this user and
with group \fB@GROUP@\fR.
.RE
As the file system may be mounted over an insecure internet connection,
this increases the risk that malicious content may be included in the file
system. So \fB@PROGRAM_NAME@\fR is slightly more restrictive than
\fBmount\fR(8).
.RS
.PP
Options \fBnosuid\fR and \fBnodev\fR will always be set; even root can not
change this.
.PP
For ordinary users to be able to mount, they must be member of group
\fB@GROUP@\fR and there must be an entry in \fIfstab\fP.
.PP
When mounted by an ordinary user, the mount point must not lie within the
home directory of another user.
.PP
If in \fIfstab\fP option \fBuid\fR and/or \fBgid\fR are given, an ordinary
user can only mount, if her uid is the one given in option \fBuid\fR and
he belongs to the group given in option \fBgid\fR.
.RE
\fBWARNING:\fR If root allows an ordinary user to mount a file system
(using \fIfstab\fP) this includes the permission to read the
associated \fBcredentials\fR from \fI@SYS_CONF_DIR@/@SECRETSFILE@\fP
as well as the \fBprivate key\fR of the associated \fBclient certificate\fR
and the mounting user may get access to this information. You should only
do this, if you might as well give this information to the user directly.
.SH URLS AND MOUNT POINTS WITH SPACES
Special characters like spaces in pathnames are a mess. They are interpreted
differently by different programs and protocols, and there are different rules
for escaping.
.PP
In \fIfstab\fP spaces must be replaced by a three digit octal escape
sequence. Write \fIhttp://foo.bar/path\(rs040with\(rs040spaces\fP instead of
\fIhttp://foo.bar/path with spaces\fP. It might also be necessary to
replace the '#'\-character by \(rs043.
.PP
For the \fI@CONFIGFILE@\fP and the \fI@SECRETSFILE@\fP files please see
the escape and quotation rules described in the \fB@CONFIGFILE@\fR(5) man page.
.PP
On \fIcommand line\fP you must obey the escaping rules of the shell.
.PP
After escaping and quotation have been removed by the respective program,
the url and mount point must resolve to exactly the same string, whether they
are taken from \fIfstab\fP, \fI@CONFIGFILE@\fP, \fI@SECRETSFILE@\fP or
the command line.
.SH CACHING
\fB@PROGRAM_NAME@\fR tries to reduce HTTP\-trafic by caching and reusing data.
Information about directories and files are held in memory, while downloaded
files are cached on disk.
.PP
\fB@PROGRAM_NAME@\fR will consider cached information about directories and file
attributes valid for a configurable time and look up this information on
the server only after this time has expired (or there is other evidence
that this information is stale). So if somebody else creates or deletes
files on the server it may take some time before the local file system
reflects this.
.PP
This will not affect the content of files and directory listings. Whenever
a file is opened, the server is looked up for a newer version of the file.
Please consult the manual \fB@CONFIGFILE@\fR(5) to see how can you configure
this according your needs.
.SH LOCKS, LOST UPDATE PROBLEM AND BACKUP FILES
WebDAV introduced locks and \fB@PROGRAM_NAME@\fR uses them by default. This will in
most cases prevent two people from changing the same file in parallel. But not
allways:
.RS
.PP
You might have disabled locks in \fI@SYS_CONF_DIR@/@CONFIGFILE@\fP or
\fI~/.@PACKAGE@/@CONFIGFILE@\fP.
.PP
The server might not support locks (they are not mandatory).
.PP
A bad connection might prevent \fB@PROGRAM_NAME@\fR from refreshing the lock
in time.
.PP
Another WebDAV\-client might use your lock (that is not too difficult and might
even happen without intention).
.RE
.PP
\fB@PROGRAM_NAME@\fR will therefore allways check if the file has been changed on the
the server before it uploads a new version. Unfortunately it has to do this in
two separate HTTP requests, as not all servers support conditional PUT. If it
finds it impossible to upload the locally changed file, it will store it in
the local backup direcotry \fIlost+found\fP. You should check this directory from
time to time and decide what to do with this files.
.PP
Sometimes locks held by some client on the server will not be released. Maybe
the client crashes or the network connection fails. When \fB@PROGRAM_NAME@\fR
finds a file locked on the server, it will check whether the lock is
held by \fB@PROGRAM_NAME@\fR and the current user, and if so tries to reuse and
release it. But this will not allways succeed. So servers should automatically
release locks after some time, when they are not refreshed by the client.
.PP
WebDAV allows to lock files that don't exist (to protect the name when a client
intends to create a new file). This locks will be displayed as files with
size 0 and last modified date of 1970\-01\-01. If this locks are not released
properly \fB@PROGRAM_NAME@\fR may not be able to access this files. You can use
\fBcadaver\fR(1) <\fIhttp://www.webdav.org/cadaver/\fP> to remove this locks.
.SH FILE OWNER AND PERMISSIONS
\fB@PACKAGE@\fR implements Unix permissions for access control. But
changing owner and permissions of a file is only \fBlocal\fR. It is
intended as a means for the owner of the file system, to controll whether
other local users may acces this file system.
.PP
The server does not know about this. From the servers point of view there is
just one user (identified by the credentials) connected. Another WebDAV\-client,
connected to the same server, is not affected by this local changes.
.PP
There is one exeption: The \fBexecute bit\fR on files is stored as a
property on the sever. You may think of this property as an information about
the type of file rather than a permission. Whether the file is executable
on the local system is still controlled by mount options and local permissions.
.PP
When the file system is unmounted, attributes of cached files (including
owner and permissions) are stored in cache, as well as the attributs of
the direcotries they are in. But there is no information stored about
directories that do not contain cached files.
.SH FILES
.TP
.I @SYS_CONF_DIR@/@CONFIGFILE@
System wide configuration file.
.TP
.I ~/.@PACKAGE@/@CONFIGFILE@
Configuration file in the users home directory.The user configuration takes
precedence over the system wide configuration. If it does not exist,
\fB@PROGRAM_NAME@\fR will will create a template file.
.TP
.I @SYS_CONF_DIR@/@SECRETSFILE@
Holds the credentials for WebDAV servers and the proxy, as well as
decryption passwords for client certificates. The file must be
read\-writable by root only.
.TP
.I ~/.@PACKAGE@/@SECRETSFILE@
Holds credentials for WebDAV servers and proxy, as well as decryption
passwords for client certificates. The file must be
read\-writable by the owner only. Credentials are first
looked up in the home directory of the mounting user. If not found
there the system wide secrets file is consulted. If no creditentials and
passwords are found they are asked from the user interactively (if not
disabled). If the file does not exist, \fB@PROGRAM_NAME@\fR will will
create a template file.
.TP
.I @SYS_CONF_DIR@/@CERTS_DIR@
You may store trusted server certificates here, that can not be verified
by use of the system wide CA\-Certificates. This is useful when your server
uses a selfmade certificate. You must configure the \fBservercert\fR option in
\fI@SYS_CONF_DIR@/@CONFIGFILE@\fP or \fI~/.@PACKAGE@/@CONFIGFILE@\fP to use
it. Certificates must be in PEM format.
.br
Be sure to verify the certificate.
.TP
.I ~/.@PACKAGE@/@CERTS_DIR@
You may store trusted server certificates here, that can not be verified
by use of the system wide CA\-Certificates. This is useful when your server
uses a selfmade certificate. You must configure the \fBservercert\fR option in
\fI~/.@PACKAGE@/@CONFIGFILE@\fP to use it. Certificates must be in PEM format.
.br
Be sure to verify the certificate.
.TP
.I @SYS_CONF_DIR@/@CERTS_DIR@/@CLICERTS_DIR@
To store client certificates. Certificates must be in PKCS#12 format. You must
configure the \fBclientcert\fR option in \fI@SYS_CONF_DIR@/@CONFIGFILE@\fP or
\fI~/.@PACKAGE@/@CONFIGFILE@\fP to use it. This directory must be rwx by root
only.
.TP
.I ~/.@PACKAGE@/@CERTS_DIR@/@CLICERTS_DIR@
To store client certificates. Certificates must be in PKCS#12 format. You must
configure the \fBclientcert\fR option in \fI~/.@PACKAGE@/@CONFIGFILE@\fP to
use it. This directory must be rwx by the owner only.
.TP
.I @SYS_RUN@
PID\-files of running mount.davfs processes are stored there. This directory
must belong to group \fB@USER@\fR with write permissions for the group and
the sticky\-bit set (mode 1775). The PID\-files are named after the mount point
of the file system.
.TP
.I @SYS_CACHE_DIR@
System wide directory for cached files. Used when the file system is
mounted by root. It must belong do group \fB@USER@\fR and read, write and
execute bits for group must be set. There is a subdirectory for every mounted
file system. The names of this subdirectories are created from url, mount
point and user name.
.TP
.I ~/.@PACKAGE@/cache
Cache directory in the mounting users home directory. For every mounted
WebDAV resource a subdirectory is created.
.RE
\fB@PROGRAM_NAME@\fR will try to create missing directories, but it will
\fBnot\fR touch \fI@SYS_CONF_DIR@\fP.
.SH ENVIRONMENT
.TP
.B https_proxy http_proxy all_proxy
If no proxy is defined in the configuration file the value is taken from
this environment variables. The proxy may be given with or without scheme
and with or without port
.br
http_proxy=[http://]foo.bar[:3218]
.br
Only used when the mounting user is root.
.TP
.B no_proxy
A comma separated list of domain names that shall be accessed directly.
\fB*\fR matches any domain name. A domain name starting with \fB.\fR
(period) matches all subdomains.
.br
Only used when the mounting user is root.
.br
Not applied when the proxy is defined in \fI@SYS_CONF_DIR@\fP.
.SH EXAMPLES
.B Non root user (e.g. filomena):
.PP
To allow an ordinary user to mount there must be an entry in \fIfstab\fP
.RS
http://webdav.org/dav /media/dav davfs noauto,user 0 0
.RE
.PP
If a proxy must be used this should be configured in
\fI@SYS_CONF_DIR@/@CONFIGFILE@\fP
.RS
proxy proxy.mycompany.com:8080
.RE
.PP
Credentials are stored in \fI/home/filomena/.@PACKAGE@/@SECRETSFILE@\fP
.RS
proxy.mycompany.com filomena "my secret"
.br
/media/dav webdav\-username password
.RE
.PP
Now the WebDAV resource may be mounted by user filomena invoking
.RS
.B mount /media/dav
.RE
.PP
and unmounted by user filomena invoking
.RS
.B umount /media/dav
.RE
.PP
.B Root user only:
.PP
Mounts the resource \fIhttps://asciigirl.com/webdav\fP at mount point
\fI/mount/site\fP, encrypting all traffic with SSL. Credentials for
\fIhttp://webdav.org/dav\fP will be looked up in \fI@SYS_CONF_DIR@/@SECRETSFILE@\fP,
if not found there the user will be asked.
.RS
.B mount \-t davfs \-o uid=otto,gid=users,mode=775 https://asciigirl.com/webdav /mount/site
.RE
.PP
Mounts the resource \fIhttp://linux.org.ar/repos\fP at \fI/dav\fP.
.RS
.B mount.davfs \-o uid=otto,gid=users,mode=775 http://linux.org.ar/repos/ /dav
.RE
.SH BUGS
\fB@PACKAGE@\fR does not support links (neither hard nor soft ones).
.SH AUTHORS
This man page was written by Luciano Bello <luciano@linux.org.ar>
for Debian, for version 0.2.3 of davfs2.
.PP
It has been updated for this version by Werner Baumann
<werner.baumann@onlinhome.de>.
.PP
@PACKAGE@ is developed by Sung Kim <hunkim@gmail.com>.
.PP
Version 1.0.0 (and later) of @PACKAGE@ is a complete rewrite
by Werner Baumann.
.SH DAVFS2 HOME
http://savannah.nongnu.org/projects/davfs2
.SH SEE ALSO
.BR u@PROGRAM_NAME@ (8),
.BR @CONFIGFILE@ (5),
.BR mount (8),
.BR umount (8),
.BR fstab (5)

1075
man/mount.davfs.8.pot Normal file

File diff suppressed because it is too large Load Diff

33
man/po4a.conf Normal file
View File

@ -0,0 +1,33 @@
# po4a configuration for davfs2 man pages 2009-04-13
# List of available languages. Two-letter language codes must
# be lower case. The list must be in one line; no line
# continuation using backslash.
[po4a_langs] de es
# For each man page there is one .pot file.
# For each language there is a subdirectory holding the Make-files,
# the PO-files, the addendum files and the translated man pages.
[po4a_paths] $master.pot $lang:$lang/$master.po
# For each translated man page there should be at least one
# addendum file holding information about the translator(s).
# It should be named after the man page with extension
# .translator. Additional addendum files may be added.
[type:man] davfs2.conf.5 \
de:de/davfs2.conf.5 add_de:de/davfs2.conf.5.translator \
es:es/davfs2.conf.5 \
opt_de:"-L UTF-8 -A UTF-8" \
opt_es:"-k 75 -L UTF-8"
[type:man] mount.davfs.8 \
de:de/mount.davfs.8 add_de:de/mount.davfs.8.translator \
opt_de:"-L UTF-8 -A UTF-8"
[type:man] umount.davfs.8 \
de:de/umount.davfs.8 add_de:de/umount.davfs.8.translator \
opt_de:"-L UTF-8 -A UTF-8"

11
man/template.translator Normal file
View File

@ -0,0 +1,11 @@
PO4A-HEADER:mode=after;position=^\.SH AUTHORS;beginboundary=^\.SH
.SH TRANSLATOR(S)
YOUR TEXT
# Please replace AUTHORS by its translation, exactly as in the .po-file.
# Translate the string TRANSLATOR(S).
# Replace YOUR TEXT with information about the translators.
# Please use the same character encoding as in the .po-file.
# Rename the file. The name should be like the name of the man
# page, with .translator appended (e.g. mount.davfs.8.translator).
# Finally remove all this comment lines (lines beginning with #).

94
man/umount.davfs.8 Normal file
View File

@ -0,0 +1,94 @@
.TH u@PROGRAM_NAME@ 8 "2009-04-13" @PACKAGE_STRING@
.SH NAME
u@PROGRAM_NAME@ \- Umount-helper to unmount a @PACKAGE@ file system
.SH SYNOPSIS
.B u@PROGRAM_NAME@ [-h | --help] [-V | --version]
.br
.BI "umount " dir
.SH SYNOPSIS (root only)
.BI "u@PROGRAM_NAME@ " dir
.SH DESCRIPTION
\fBu@PROGRAM_NAME@\fR is a umount helper program. It is called by the
\fBumount\fR(8) command. Its purpose is to prevent the umount command
from returning unless \fB@PROGRAM_NAME@\fR has synchronized all its
cached files with the webdav server.
.PP
\fIdir\fP is the mountpoint where the WebDAV resource is mounted on.
It may be an absolute or relative path.
.PP
While for local file systems \fBumount\fR(8) will only return when all
cached data have been written to disk, this is not automatically true
for a mounted \fB@PACKAGE@\fR file system. With this umount helper the
user can rely on the familiar behaviour of \fBumount\fR(8). To inform
the operating system that the file system uses a network connection,
you should always use the \fB_netdev\fR option, when mounting as
\fB@PACKAGE@\fR file system.
.PP
Depending on the amount of data and the quality of the connection, unmounting
a \fB@PACKAGE@\fR file system may take some seconds up to some hours.
.PP
If the \fB@PROGRAM_NAME@\fR daemon encountered serious errors,
\fBu@PROGRAM_NAME@\fR may return an error instead of unmounting the file
system. In this case try \fBumount -i\fR. The \fB-i\fR option will prevent
\fBumount\fR(8) from calling \fBu@PROGRAM_NAME@\fR.
.SH OPTIONS
.TP
.B -V --version
Output version.
.TP
.B -h --help
Print a help message.
.TP
.B -f -l -n -r -v
This options are \fBignored\fR. They are only recognized for compatibility
with \fBumount\fR(8).
.SH FILES
.TP
.I @SYS_RUN@
PID-files of running \fBu@PROGRAM_NAME@\fR processes are looked up here.
.SH BUGS
No known bugs.
.SH AUTHORS
This man page was written by Werner Baumann <werner.baumann@onlinehome.de>.
.SH DAVFS2 HOME
http://savannah.nongnu.org/projects/davfs2
.SH SEE ALSO
.BR @PROGRAM_NAME@ (8),
.BR umount (8),
.BR @CONFIGFILE@ (5),
.BR fstab (5)

225
man/umount.davfs.8.pot Normal file
View File

@ -0,0 +1,225 @@
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2009-04-13 21:30+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: ENCODING"
# type: TH
#: davfs2.conf.5:1 mount.davfs.8:1 umount.davfs.8:1
#, no-wrap
msgid "2009-04-13"
msgstr ""
# type: TH
#: davfs2.conf.5:1 mount.davfs.8:1 umount.davfs.8:1
#, no-wrap
msgid "@PACKAGE_STRING@"
msgstr ""
# type: SH
#: davfs2.conf.5:4 mount.davfs.8:3 umount.davfs.8:3
#, no-wrap
msgid "NAME"
msgstr ""
# type: SH
#: davfs2.conf.5:9 mount.davfs.8:22 umount.davfs.8:20
#, no-wrap
msgid "DESCRIPTION"
msgstr ""
# type: SH
#: davfs2.conf.5:501 mount.davfs.8:514 umount.davfs.8:79
#, no-wrap
msgid "AUTHORS"
msgstr ""
# type: SH
#: davfs2.conf.5:507 mount.davfs.8:531 umount.davfs.8:84
#, no-wrap
msgid "DAVFS2 HOME"
msgstr ""
# type: Plain text
#: davfs2.conf.5:510 mount.davfs.8:534 umount.davfs.8:87
msgid "http://savannah.nongnu.org/projects/davfs2"
msgstr ""
# type: SH
#: davfs2.conf.5:512 mount.davfs.8:536 umount.davfs.8:89
#, no-wrap
msgid "SEE ALSO"
msgstr ""
# type: SH
#: mount.davfs.8:8 umount.davfs.8:8
#, no-wrap
msgid "SYNOPSIS"
msgstr ""
# type: SH
#: mount.davfs.8:15 umount.davfs.8:15
#, no-wrap
msgid "SYNOPSIS (root only)"
msgstr ""
# type: Plain text
#: mount.davfs.8:61 umount.davfs.8:30
msgid ""
"I<dir> is the mountpoint where the WebDAV resource is mounted on. It may be "
"an absolute or relative path."
msgstr ""
# type: SH
#: mount.davfs.8:68 umount.davfs.8:51
#, no-wrap
msgid "OPTIONS"
msgstr ""
# type: TP
#: mount.davfs.8:70 umount.davfs.8:53
#, no-wrap
msgid "B<-V --version>"
msgstr ""
# type: Plain text
#: mount.davfs.8:73 umount.davfs.8:56
msgid "Output version."
msgstr ""
# type: TP
#: mount.davfs.8:74 umount.davfs.8:57
#, no-wrap
msgid "B<-h --help>"
msgstr ""
# type: Plain text
#: mount.davfs.8:77 umount.davfs.8:60
msgid "Print a help message."
msgstr ""
# type: SH
#: mount.davfs.8:345 umount.davfs.8:67
#, no-wrap
msgid "FILES"
msgstr ""
# type: TP
#: mount.davfs.8:406 umount.davfs.8:69
#, no-wrap
msgid "I<@SYS_RUN@>"
msgstr ""
# type: SH
#: mount.davfs.8:509 umount.davfs.8:74
#, no-wrap
msgid "BUGS"
msgstr ""
# type: TH
#: umount.davfs.8:1
#, no-wrap
msgid "u@PROGRAM_NAME@"
msgstr ""
# type: Plain text
#: umount.davfs.8:6
msgid "u@PROGRAM_NAME@ - Umount-helper to unmount a @PACKAGE@ file system"
msgstr ""
# type: Plain text
#: umount.davfs.8:11
msgid "B<u@PROGRAM_NAME@ [-h | --help] [-V | --version]>"
msgstr ""
# type: Plain text
#: umount.davfs.8:13
msgid "B<umount >I<dir>"
msgstr ""
# type: Plain text
#: umount.davfs.8:18
msgid "B<u@PROGRAM_NAME@ >I<dir>"
msgstr ""
# type: Plain text
#: umount.davfs.8:26
msgid ""
"B<u@PROGRAM_NAME@> is a umount helper program. It is called by the B<umount>"
"(8) command. Its purpose is to prevent the umount command from returning "
"unless B<@PROGRAM_NAME@> has synchronized all its cached files with the "
"webdav server."
msgstr ""
# type: Plain text
#: umount.davfs.8:39
msgid ""
"While for local file systems B<umount>(8) will only return when all cached "
"data have been written to disk, this is not automatically true for a mounted "
"B<@PACKAGE@> file system. With this umount helper the user can rely on the "
"familiar behaviour of B<umount>(8). To inform the operating system that the "
"file system uses a network connection, you should always use the B<_netdev> "
"option, when mounting as B<@PACKAGE@> file system."
msgstr ""
# type: Plain text
#: umount.davfs.8:43
msgid ""
"Depending on the amount of data and the quality of the connection, "
"unmounting a B<@PACKAGE@> file system may take some seconds up to some hours."
msgstr ""
# type: Plain text
#: umount.davfs.8:49
msgid ""
"If the B<@PROGRAM_NAME@> daemon encountered serious errors, "
"B<u@PROGRAM_NAME@> may return an error instead of unmounting the file "
"system. In this case try B<umount -i>. The B<-i> option will prevent "
"B<umount>(8) from calling B<u@PROGRAM_NAME@>."
msgstr ""
# type: TP
#: umount.davfs.8:61
#, no-wrap
msgid "B<-f -l -n -r -v>"
msgstr ""
# type: Plain text
#: umount.davfs.8:65
msgid ""
"This options are B<ignored>. They are only recognized for compatibility with "
"B<umount>(8)."
msgstr ""
# type: Plain text
#: umount.davfs.8:72
msgid "PID-files of running B<u@PROGRAM_NAME@> processes are looked up here."
msgstr ""
# type: Plain text
#: umount.davfs.8:77
msgid "No known bugs."
msgstr ""
# type: Plain text
#: umount.davfs.8:82
msgid ""
"This man page was written by Werner Baumann E<lt>werner.baumann@onlinehome."
"deE<gt>."
msgstr ""
# type: Plain text
#: umount.davfs.8:94
msgid "B<@PROGRAM_NAME@>(8), B<umount>(8), B<@CONFIGFILE@>(5), B<fstab>(5)"
msgstr ""