Tell me this - set me straight!
the --delete option says "delete files that don't exist on the sending side"
Does this mean and only mean that it will delete files from the DESTINATION that DON'T EXIST on the sending side? :confused: (2 Replies)
Tell me this - set me straight!
The --delete option says "delete files that don't exist on the sending side"
Does this mean and only mean that it will delete files from the DESTINATION that DON'T EXIST on the sending side? :confused: (1 Reply)
Hi there
Does anybody know of a way that i can, instead of issuing a --delete when syncing one directory to another, I can instead somehow receive a list of what would be deleted, but not actually delete it ?
basically, people are occasionally putting files into one of synced folders, but... (2 Replies)
When I try to back up my libraries with
rsync -azv --delete -e ssh /home/sarah/ saga:/home/sarah/bupembladaily/
I get error message
rsync: readlink_stat("/home/sarah/.gvfs") failed: Permission denied (13)
FATAL I/O ERROR: dying to avoid a --delete-during issue with a pre-3.0.7 receiver.... (7 Replies)
Hi All,
I have RHEL 5.6 with a 70GB local directory of Web content. Images, PHP scripts etc.
I need to copy all this content to an NFS array thats mounted on the RHEL server.
I did a baseline cp to copy the content one week ago. Since my baseline copy the local directory has grown by 8GB.... (2 Replies)
Hi,
I need to use rsync to delete multiple files(only specified files not all) using --delete option, these files are located in different target folders.
Instead of running rsync command multiple times for each file, can we achieve this with one time execution?
your help is much... (0 Replies)
Hello all,
I have a problem with rsync command.
From a backup server, I use a command like the one below:
rsync -av --delete user@host:/home/user/ /home/backup_user/daily_rotating_backup/
In some folders of the user there are some files on which he has removed his write permission on... (3 Replies)
rsync with --delete won't honor the delete if the source is something/*. I want the delete to work, but not to delete directories on the target that are peer to the intended directory. For example, using these source and target file structures:
Source on desktop:
~/
Money/
... (4 Replies)
I have a script that synchronises a directory to a DR server, but to improve the time, I actually use rsync to transfer files * in one batch and also
* in another batch - both batches run from the same script and run in the background.
My problem is that there isn't much space on the... (1 Reply)
Discussion started by: Catullus
1 Replies
LEARN ABOUT DEBIAN
slack.conf
slack.conf(5) File Formats Manual slack.conf(5)NAME
slack.conf - configuration file for slack
DESCRIPTION
The file /etc/slack.conf contains configuration information for slack(8) and its backends. It should contain one keyword-value pair per
line, separated by an '=' sign. Keywords must consist solely of capital letters and underscores. Values may take any appropriate format,
but must not begin with a space. Comments start with '#', and all text from the '#' to the end of a line is ignored. Trailing whitespace
on lines is ignored. Empty lines or lines consisting of only whitespace and comments are ignored.
Valid keywords are:
SOURCE The master source for slack roles. It can be in one of four forms:
o /path/to/dir
Use a local directory.
o somehost:/path/to/dir
Use given directory on a remote host via rsync over SSH.
o rsync://somehost/module
Use module on a remote rsyncd server (directly over the network).
o somehost::module
Use the rsync daemon protocol over SSH to the given host. See "USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION" in
rsync(1)
All forms of SOURCE are passed directly to rsync, so you can do things like add "user@" before the host on any remote forms. For
more about what rsync can do, see its manual page, of course.
For the last form, however, we do a little magic. rsync treats the last two forms equivalently, so we overload the last form by
automatically passing "-e ssh" to rsync when we see it. This hack lets us tell slack to use this nice feature of rsync just using
the SOURCE config option.
ROOT The root filesystem into which to install slack roles. Usually '/'.
ROLE_LIST
The location of the role list, which lists the roles to be installed by default on each host.
This can be a path relative to the source, or can be an entirely separate location if it starts with a slash or a hostname (option-
ally preceeded by user@).
CACHE A local cache directory, used as a local mirror of the SOURCE.
STAGE A local staging directory, used as an intermediate stage when installing files.
BACKUP_DIR
A directory in which to keep dated backups for rollbacks.
EXAMPLE
A typical file might look like this:
# slack.conf configuration file
SOURCE=slack-master:/slack # source is on a remote
# host named "slack-master"
ROLE_LIST=slack-master:/roles.conf
ROOT=/
CACHE=/var/cache/slack
STAGE=/var/lib/slack/stage
BACKUP_DIR=/var/lib/slack/backups
FILES
/etc/slack.conf
SEE ALSO slack(8), rsync(1)File formats 2005-05-23 slack.conf(5)