I have 2 servers syncing some directories with an rsync script. They are in different countries. The rsync script is executed on Server#1. I am using 'fswatch' to execute the script automatically, when the directory is modified.
Here is where I am looking for help:
After 'fswatch' see's a directory change, it triggers my rsync script on Server#1. I need the rsync script to look at the Server#2 and check a file which contains the string "open" or "closed". If it says "closed", I want the rsync to script to execute. If it says "open", I don't want the rsync script to execute, but rather wait x seconds and check the file again (the file will eventually change to "closed", allowing the script to run).
Any insight on structuring this is greatly appreciated, I haven't figured out how to setup the loop of 'check file/don't execute/wait/check again' logic.
---------- Post updated at 08:06 PM ---------- Previous update was at 06:44 PM ----------
I think I found the logic. Can somebody tell me how to get this to time out after say 100 tries?
Last edited by sudo; 05-16-2014 at 09:25 PM..
Reason: Removing code
Sorry for such a dreadful title, but I'm not sure how to be more descriptive. I'm hoping some of the more gurutastic out there can take a look at a solution I came up with to a problem, and advice if there are better ways to have gone about it.
To make a long story short around 20K pieces of... (2 Replies)
I'm trying to understand if it's possible to create a set of variables that are numbered based on another variable (using eval) in a loop, and then call on it before the loop ends.
As an example I've written a script called question (The fist command is to show what is the contents of the... (2 Replies)
Hi Im running this script, which is supposed to find the max value build some tables and then stop running once all the tables are built. Thing is , it keeps assigning a null value to $h and then $g is null so it keep building tables i.e. testupdateNUL. How can I stop this? Here is what I have:
... (4 Replies)
Hi all
Sorry for the basic question, but i am writing a shell script to get around a slightly flaky binary that ships with one of our servers. This particular utility randomly generates the correct information and could work first time or may work on the 12th or 100th attempt etc !.... (4 Replies)
Hi,
hope I am posting in the right section.
My problem is that I have 2 or more arguments passed and I want to check if the arguments passed exists or not.
The first argument should not exist and the remaining others should exist.
example:
./shells.sh argument1 argument2 argument3
... (5 Replies)
Hi, I was debating if I should put this in the dummies or scripts section, I apologize in advance if I chose poorly.
Fairly new to Unix and BASH scripting but I thought I made it fairly well given my limited understanding. However, the output indicates that it's looping and I'm ending up with a... (5 Replies)
Hello All,
Maybe I'm Missing something here but I have NOOO idea what the heck is going on with this....?
I have a Variable that contains a PATTERN of what I'm considering "Illegal Characters". So what I'm doing is looping
through a string containing some of these "Illegal Characters". Now... (5 Replies)
Hi,
I want to read file multiple times. Right now i am using while loop but that is not working.
ex.
While read line
do
while read line2
do
echo stmt1
#processing some data based on data.,
done < file2.txt
done < file1.txt # This will have 10... (4 Replies)
Hi all,
i developed a script to measure the uptime of a process in a Solaris 10/11 environments.
All is well, but i came across a situation where there are multiple processes of the same name. Basically i have the following result file:
beVWARS 13357 19592122
beVWARS 14329 19591910... (4 Replies)
Discussion started by: nms
4 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)