File: control

package info (click to toggle)
fssync 1.6-1.1
  • links: PTS
  • area: main
  • in suites: bookworm, bullseye, sid
  • size: 176 kB
  • sloc: python: 1,468; makefile: 27
file content (39 lines) | stat: -rw-r--r-- 1,762 bytes parent folder | download | duplicates (2)
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
Source: fssync
Section: utils
Priority: extra
Maintainer: Julien Muchembled <jm@jmuchemb.eu>
# python3-pylibacl is only for dh_auto_test
Build-Depends: debhelper (>= 10), python3-docutils, python3-pylibacl (>> 0.5.1-1.1)
Standards-Version: 3.9.8
Homepage: http://jmuchemb.eu/fssync.git
Vcs-Git: git://jmuchemb.eu/fssync.git

Package: fssync
Architecture: all
Depends: ${misc:Depends}, python3 (>= 3.3), python3-pylibacl (>> 0.5.1-1.1), openssh-client | openssh-server
Description: File system synchronization tool (1-way, over SSH)
 fssync is a 1-way file-synchronization tool that tracks inodes and maintains a
 local database of files that are on the remote side, making it able to:
  - handle efficiently a huge number of dirs/files
  - detect renames/moves and hard-links
 .
 It aims at minimizing network traffic and synchronizing every detail of a file
 system:
  - all types of inode: file, dir, block/character/fifo, socket, symlink
  - preserve hard links
  - modification time, ownership/permission/ACL, extended attributes
  - sparse files
 .
 Other features:
  - it can be configured to exclude files from synchronization
  - fssync can be interrupted and resumed at any time, making it tolerant to
    random failures (e.g. network error)
  - algorithm to synchronize file content is designed to handle big files
    like VM images efficiently, by updating fixed-size modified blocks in-place
 .
 Main usage of fssync is to prevent data loss in case of hardware failure,
 where RAID1 is not possible (e.g. in laptops).
 .
 On Btrfs file systems, fssync is an useful alternative to `btrfs send` (and
 `receive`) commands, thanks to filtering capabilities. This can be combined
 with Btrfs snapshotting at destination side for a full backup solution.