10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I wish to copy all the files & folder under /web/Transfer_Files/data/ on mymac1 (Linux) to remote server mybank.intra.com (Solaris 10) /tmp/ location
I am using Ansible tool synchronize module which triggers the unix rsync command as below:rsync --delay-updates -F --compress --archive --rsh=ssh... (2 Replies)
Discussion started by: mohtashims
2 Replies
2. Shell Programming and Scripting
Wondering if anyone can point me to an example of how to setup a bash script that executes cp mv and rsync commands and only sends an email if there were errors with any of those commands and what the errors are. In addition it should email if the cron event to execute the script fails, or in... (1 Reply)
Discussion started by: consultant
1 Replies
3. UNIX for Dummies Questions & Answers
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Discussion started by: okonita
3 Replies
4. UNIX and Linux Applications
So I have this rsync script I wrote to grab some sql files and import them to a database. I left in the mysql stuff just give context to the situation. The real problem is with my rsync code.
script.sh (chmod 744)
#!/bin/sh
rsync -av --rsh="sshpass -p'PASSWORD' ssh -l'USERNAME'"... (3 Replies)
Discussion started by: noPermissions
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I've created a cron job for a script with a rsync command in it. The script is named pull.sh and contains the following line :
What it is supposed to do is pull backup files from the production server of my company to my local server. It should also generate the log file (output.log)... (1 Reply)
Discussion started by: anaigini45
1 Replies
6. UNIX for Advanced & Expert Users
Hi,
I am able to use rsync and run it thro' command line. But when I schedule a script file that has rsync command thro' cron, the job doesn't get executed. All other jobs in the cron runs fine.
cron entry--
57 13 * * * /home/apm/cron/rsync-backup.sh
rsync-backup.sh file--
rsync -avz... (1 Reply)
Discussion started by: sm23328
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am able to use rsync and run it thro' command line. But when I schedule a script file that has rsync command thro' cron, the job doesn't get executed. All other jobs in the cron runs fine.
cron entry--
57 13 * * * /home/apm/cron/rsync-backup.sh
rsync-backup.sh file--
rsync -avz... (1 Reply)
Discussion started by: sm23328
1 Replies
8. Shell Programming and Scripting
I have the following rsync script that I use for syncing MySQL files from one server to another. I run the script at 20 minutes past every second hour in cron. I want to make sure that the script completes in it's entirety before it is set to kick off again. For example, when the script starts at... (3 Replies)
Discussion started by: sunsysadm2003
3 Replies
9. AIX
Hi,
I can use 'crontabs –e' and do all the scheduling I like. However I would like to auto send myself just the cronjobs logs that fail. That is to say the PIDs that fail and the related lines with those PID’s only. (Not the full set of logs) Has anyone done this work? Or does an AIX 5.3 tool... (0 Replies)
Discussion started by: Keith Johnson
0 Replies
10. UNIX for Advanced & Expert Users
Hi,
I am running a rsync via cron job.
Its running fine and is scheduled to 9:00 AM everyday.
Sometimes it runs for more than 24 hours, such that the next days cron also fires.
Now how will the sync happen as the <sync file> that both crons have created might conflict.
Thanks (5 Replies)
Discussion started by: vibhor_agarwali
5 Replies
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)