2019-02-09 10:42:57 +00:00
---
title: "rclone serve dlna"
2020-05-16 14:11:55 +00:00
description: "Serve remote:path over DLNA"
2019-02-09 10:42:57 +00:00
slug: rclone_serve_dlna
url: /commands/rclone_serve_dlna/
2020-02-10 12:31:45 +00:00
# autogenerated - DO NOT EDIT, instead edit the source code in cmd/serve/dlna/ and as part of making a release run "make commanddocs"
2019-02-09 10:42:57 +00:00
---
2020-05-22 10:17:37 +00:00
# rclone serve dlna
2019-02-09 10:42:57 +00:00
Serve remote:path over DLNA
2020-05-22 10:17:37 +00:00
## Synopsis
2019-02-09 10:42:57 +00:00
2020-05-25 10:59:33 +00:00
rclone serve dlna is a DLNA media server for media stored in an rclone remote. Many
2019-02-09 10:42:57 +00:00
devices, such as the Xbox and PlayStation, can automatically discover this server in the LAN
and play audio/video from it. VLC is also supported. Service discovery uses UDP multicast
packets (SSDP) and will thus only work on LANs.
Rclone will list all files present in the remote, without filtering based on media formats or
file extensions. Additionally, there is no media transcoding support. This means that some
players might show files that they are not able to play back correctly.
2020-05-22 10:17:37 +00:00
## Server options
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
Use `--addr` to specify which IP address and port the server should
2021-02-02 13:42:35 +00:00
listen on, e.g. `--addr 1.2.3.4:8000` or `--addr :8080` to listen to all
2019-02-09 10:42:57 +00:00
IPs.
2020-09-02 15:59:04 +00:00
Use `--name` to choose the friendly server name, which is by
2019-06-15 11:01:29 +00:00
default "rclone (hostname)".
2020-09-02 15:59:04 +00:00
Use `--log-trace` in conjunction with `-vv` to enable additional debug
2019-06-15 11:01:29 +00:00
logging of all UPNP traffic.
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
## VFS - Virtual File System
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
This command uses the VFS layer. This adapts the cloud storage objects
that rclone uses into something which looks much more like a disk
filing system.
Cloud storage objects have lots of properties which aren't like disk
files - you can't extend them or write to the middle of them, so the
VFS layer has to deal with that. Because there is no one right way of
doing this there are various options explained below.
The VFS layer also implements a directory cache - this caches info
about files and directories (but not the data) in memory.
## VFS Directory Cache
Using the `--dir-cache-time` flag, you can control how long a
2019-02-09 10:42:57 +00:00
directory should be considered up to date and not refreshed from the
2020-09-02 15:59:04 +00:00
backend. Changes made through the mount will appear immediately or
invalidate the cache.
--dir-cache-time duration Time to cache directory entries for. (default 5m0s)
2021-06-08 15:57:04 +00:00
--poll-interval duration Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable. (default 1m0s)
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
However, changes made directly on the cloud storage by the web
interface or a different copy of rclone will only be picked up once
the directory cache expires if the backend configured does not support
polling for changes. If the backend supports polling, changes will be
picked up within the polling interval.
You can send a `SIGHUP` signal to rclone for it to flush all
directory caches, regardless of how old they are. Assuming only one
rclone instance is running, you can reset the cache like this:
2019-02-09 10:42:57 +00:00
kill -SIGHUP $(pidof rclone)
If you configure rclone with a [remote control ](/rc ) then you can use
rclone rc to flush the whole directory cache:
rclone rc vfs/forget
Or individual files or directories:
rclone rc vfs/forget file=path/to/file dir=path/to/dir
2020-09-02 15:59:04 +00:00
## VFS File Buffering
2019-02-09 10:42:57 +00:00
The `--buffer-size` flag determines the amount of memory,
that will be used to buffer data in advance.
2020-09-02 15:59:04 +00:00
Each open file will try to keep the specified amount of data in memory
at all times. The buffered data is bound to one open file and won't be
shared.
This flag is a upper limit for the used memory per open file. The
buffer will only use memory for data that is downloaded but not not
yet read. If the buffer is empty, only a small amount of memory will
be used.
2019-02-09 10:42:57 +00:00
The maximum memory used by rclone for buffering can be up to
`--buffer-size * open files` .
2020-09-02 15:59:04 +00:00
## VFS File Caching
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
These flags control the VFS file caching options. File caching is
necessary to make the VFS layer appear compatible with a normal file
system. It can be disabled at the cost of some compatibility.
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
For example you'll need to enable VFS caching if you want to read and
write simultaneously to a file. See below for more details.
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
Note that the VFS cache is separate from the cache backend and you may
find that you need one or the other or both.
2019-02-09 10:42:57 +00:00
--cache-dir string Directory rclone will use for caching.
2020-09-02 15:59:04 +00:00
--vfs-cache-mode CacheMode Cache mode off|minimal|writes|full (default off)
2019-02-09 10:42:57 +00:00
--vfs-cache-max-age duration Max age of objects in the cache. (default 1h0m0s)
2020-09-02 15:59:04 +00:00
--vfs-cache-max-size SizeSuffix Max total size of objects in the cache. (default off)
2019-02-09 10:42:57 +00:00
--vfs-cache-poll-interval duration Interval to poll the cache for stale objects. (default 1m0s)
2020-09-02 15:59:04 +00:00
--vfs-write-back duration Time to writeback files after last use when using cache. (default 5s)
2019-02-09 10:42:57 +00:00
If run with `-vv` rclone will print the location of the file cache. The
files are stored in the user cache file area which is OS dependent but
can be controlled with `--cache-dir` or setting the appropriate
environment variable.
The cache has 4 different modes selected by `--vfs-cache-mode` .
The higher the cache mode the more compatible rclone becomes at the
cost of using disk space.
Note that files are written back to the remote only when they are
2020-09-02 15:59:04 +00:00
closed and if they haven't been accessed for --vfs-write-back
second. If rclone is quit or dies with files that haven't been
uploaded, these will be uploaded next time rclone is run with the same
flags.
2019-02-09 10:42:57 +00:00
2021-02-02 13:42:35 +00:00
If using `--vfs-cache-max-size` note that the cache may exceed this size
2019-02-09 10:42:57 +00:00
for two reasons. Firstly because it is only checked every
2021-02-02 13:42:35 +00:00
`--vfs-cache-poll-interval` . Secondly because open files cannot be
2019-02-09 10:42:57 +00:00
evicted from the cache.
2021-03-31 18:12:08 +00:00
You **should not** run two copies of rclone using the same VFS cache
with the same or overlapping remotes if using `--vfs-cache-mode > off` .
This can potentially cause data corruption if you do. You can work
around this by giving each rclone its own cache hierarchy with
`--cache-dir` . You don't need to worry about this if the remotes in
use don't overlap.
2020-05-22 10:17:37 +00:00
### --vfs-cache-mode off
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
In this mode (the default) the cache will read directly from the remote and write
2019-02-09 10:42:57 +00:00
directly to the remote without caching anything on disk.
This will mean some operations are not possible
* Files can't be opened for both read AND write
* Files opened for write can't be seeked
* Existing files opened for write must have O_TRUNC set
* Files open for read with O_TRUNC will be opened write only
* Files open for write only will behave as if O_TRUNC was supplied
* Open modes O_APPEND, O_TRUNC are ignored
* If an upload fails it can't be retried
2020-05-22 10:17:37 +00:00
### --vfs-cache-mode minimal
2019-02-09 10:42:57 +00:00
This is very similar to "off" except that files opened for read AND
2020-09-02 15:59:04 +00:00
write will be buffered to disk. This means that files opened for
2019-02-09 10:42:57 +00:00
write will be a lot more compatible, but uses the minimal disk space.
These operations are not possible
* Files opened for write only can't be seeked
* Existing files opened for write must have O_TRUNC set
* Files opened for write only will ignore O_APPEND, O_TRUNC
* If an upload fails it can't be retried
2020-05-22 10:17:37 +00:00
### --vfs-cache-mode writes
2019-02-09 10:42:57 +00:00
In this mode files opened for read only are still read directly from
the remote, write only and read/write files are buffered to disk
first.
This mode should support all normal file system operations.
2020-09-02 15:59:04 +00:00
If an upload fails it will be retried at exponentially increasing
intervals up to 1 minute.
2019-02-09 10:42:57 +00:00
2020-05-22 10:17:37 +00:00
### --vfs-cache-mode full
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
In this mode all reads and writes are buffered to and from disk. When
data is read from the remote this is buffered to disk as well.
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
In this mode the files in the cache will be sparse files and rclone
2021-02-02 13:42:35 +00:00
will keep track of which bits of the files it has downloaded.
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
So if an application only reads the starts of each file, then rclone
will only buffer the start of the file. These files will appear to be
their full size in the cache, but they will be sparse files with only
the data that has been downloaded present in them.
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
This mode should support all normal file system operations and is
otherwise identical to --vfs-cache-mode writes.
When reading a file rclone will read --buffer-size plus
--vfs-read-ahead bytes ahead. The --buffer-size is buffered in memory
whereas the --vfs-read-ahead is buffered on disk.
When using this mode it is recommended that --buffer-size is not set
too big and --vfs-read-ahead is set large if required.
2021-02-02 13:42:35 +00:00
**IMPORTANT** not all file systems support sparse files. In particular
FAT/exFAT do not. Rclone will perform very badly if the cache
directory is on a filesystem which doesn't support sparse files and it
will log an ERROR message if one is detected.
2020-09-02 15:59:04 +00:00
## VFS Performance
These flags may be used to enable/disable features of the VFS for
performance or other reasons.
In particular S3 and Swift benefit hugely from the --no-modtime flag
(or use --use-server-modtime for a slightly different effect) as each
read of the modification time takes a transaction.
--no-checksum Don't compare checksums on up/download.
--no-modtime Don't read/write the modification time (can speed things up).
--no-seek Don't allow seeking in files.
--read-only Mount read-only.
When rclone reads files from a remote it reads them in chunks. This
means that rather than requesting the whole file rclone reads the
chunk specified. This is advantageous because some cloud providers
account for reads being all the data requested, not all the data
delivered.
Rclone will keep doubling the chunk size requested starting at
--vfs-read-chunk-size with a maximum of --vfs-read-chunk-size-limit
unless it is set to "off" in which case there will be no limit.
--vfs-read-chunk-size SizeSuffix Read the source objects in chunks. (default 128M)
--vfs-read-chunk-size-limit SizeSuffix Max chunk doubling size (default "off")
Sometimes rclone is delivered reads or writes out of order. Rather
than seeking rclone will wait a short time for the in sequence read or
write to come in. These flags only come into effect when not using an
on disk cache file.
2019-02-09 10:42:57 +00:00
2020-09-02 15:59:04 +00:00
--vfs-read-wait duration Time to wait for in-sequence read before seeking. (default 20ms)
--vfs-write-wait duration Time to wait for in-sequence write before giving error. (default 1s)
2019-02-09 10:42:57 +00:00
2021-02-02 13:42:35 +00:00
When using VFS write caching (--vfs-cache-mode with value writes or full),
the global flag --transfers can be set to adjust the number of parallel uploads of
modified files from cache (the related global flag --checkers have no effect on mount).
--transfers int Number of file transfers to run in parallel. (default 4)
2020-09-02 15:59:04 +00:00
## VFS Case Sensitivity
2020-02-10 14:52:31 +00:00
Linux file systems are case-sensitive: two files can differ only
by case, and the exact case must be used when opening a file.
File systems in modern Windows are case-insensitive but case-preserving:
although existing files can be opened using any case, the exact case used
to create the file is preserved and available for programs to query.
It is not allowed for two files in the same directory to differ only by case.
2020-05-25 10:59:33 +00:00
Usually file systems on macOS are case-insensitive. It is possible to make macOS
2020-02-10 14:52:31 +00:00
file systems case-sensitive but that is not the default
2021-02-02 13:42:35 +00:00
The `--vfs-case-insensitive` mount flag controls how rclone handles these
2020-02-10 14:52:31 +00:00
two cases. If its value is "false", rclone passes file names to the mounted
2020-09-02 15:59:04 +00:00
file system as-is. If the flag is "true" (or appears without a value on
2020-02-10 14:52:31 +00:00
command line), rclone may perform a "fixup" as explained below.
The user may specify a file name to open/delete/rename/etc with a case
different than what is stored on mounted file system. If an argument refers
to an existing file with exactly the same name, then the case of the existing
file on the disk will be used. However, if a file name with exactly the same
name is not found but a name differing only by case exists, rclone will
transparently fixup the name. This fixup happens only when an existing file
is requested. Case sensitivity of file names created anew by rclone is
controlled by an underlying mounted file system.
Note that case sensitivity of the operating system running rclone (the target)
may differ from case sensitivity of a file system mounted by rclone (the source).
The flag controls whether "fixup" is performed to satisfy the target.
2020-09-02 15:59:04 +00:00
If the flag is not provided on the command line, then its default value depends
2020-05-25 10:59:33 +00:00
on the operating system where rclone runs: "true" on Windows and macOS, "false"
2020-02-10 14:52:31 +00:00
otherwise. If the flag is provided without a value, then it is "true".
2021-03-31 18:12:08 +00:00
## Alternate report of used bytes
Some backends, most notably S3, do not report the amount of bytes used.
If you need this information to be available when running `df` on the
filesystem, then pass the flag `--vfs-used-is-size` to rclone.
With this flag set, instead of relying on the backend to report this
information, rclone will scan the whole remote similar to `rclone size`
and compute the total used space itself.
_WARNING._ Contrary to `rclone size` , this flag ignores filters so that the
result is accurate. However, this is very inefficient and may cost lots of API
calls resulting in extra charges. Use it as a last resort and only with caching.
2019-02-09 10:42:57 +00:00
```
rclone serve dlna remote:path [flags]
```
2020-05-22 10:17:37 +00:00
## Options
2019-02-09 10:42:57 +00:00
```
--addr string ip:port or :port to bind the DLNA http server to. (default ":7879")
--dir-cache-time duration Time to cache directory entries for. (default 5m0s)
--dir-perms FileMode Directory permissions (default 0777)
--file-perms FileMode File permissions (default 0666)
2021-02-02 13:42:35 +00:00
--gid uint32 Override the gid field set by the filesystem. Not supported on Windows. (default 1000)
2019-02-09 10:42:57 +00:00
-h, --help help for dlna
2019-06-15 11:01:29 +00:00
--log-trace enable trace logging of SOAP traffic
--name string name of DLNA server
2019-02-09 10:42:57 +00:00
--no-checksum Don't compare checksums on up/download.
--no-modtime Don't read/write the modification time (can speed things up).
--no-seek Don't allow seeking in files.
--poll-interval duration Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable. (default 1m0s)
--read-only Mount read-only.
2021-02-02 13:42:35 +00:00
--uid uint32 Override the uid field set by the filesystem. Not supported on Windows. (default 1000)
2021-07-20 18:45:41 +00:00
--umask int Override the permission bits set by the filesystem. Not supported on Windows. (default 2)
2019-02-09 10:42:57 +00:00
--vfs-cache-max-age duration Max age of objects in the cache. (default 1h0m0s)
--vfs-cache-max-size SizeSuffix Max total size of objects in the cache. (default off)
--vfs-cache-mode CacheMode Cache mode off|minimal|writes|full (default off)
--vfs-cache-poll-interval duration Interval to poll the cache for stale objects. (default 1m0s)
2019-10-26 10:04:54 +00:00
--vfs-case-insensitive If a file name not found, find a case insensitive match.
2020-09-02 15:59:04 +00:00
--vfs-read-ahead SizeSuffix Extra read ahead over --buffer-size when using cache-mode full.
2021-06-08 15:57:04 +00:00
--vfs-read-chunk-size SizeSuffix Read the source objects in chunks. (default 128Mi)
2019-02-09 10:42:57 +00:00
--vfs-read-chunk-size-limit SizeSuffix If greater than --vfs-read-chunk-size, double the chunk size after each chunk read, until the limit is reached. 'off' is unlimited. (default off)
2020-05-22 10:17:37 +00:00
--vfs-read-wait duration Time to wait for in-sequence read before seeking. (default 20ms)
2021-03-31 18:12:08 +00:00
--vfs-used-is-size rclone size Use the rclone size algorithm for Used size.
2020-09-02 15:59:04 +00:00
--vfs-write-back duration Time to writeback files after last use when using cache. (default 5s)
2020-05-16 14:11:55 +00:00
--vfs-write-wait duration Time to wait for in-sequence write before giving error. (default 1s)
2019-02-09 10:42:57 +00:00
```
2019-06-20 15:18:02 +00:00
See the [global flags page ](/flags/ ) for global options not listed here.
2020-05-22 10:17:37 +00:00
## SEE ALSO
2019-02-09 10:42:57 +00:00
* [rclone serve ](/commands/rclone_serve/ ) - Serve a remote over a protocol.
