From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Package request: fswatch
Date: Tue, 14 Feb 2017 02:47:00 -0000 [thread overview]
Message-ID: <4925792d-5253-b159-aff1-8b15bdeb4432@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAABYpSiQVASBNiEUsJYgMx3WsYTDxYhbKi-XpjpFzU9qFVMEwg@mail.gmail.com>
On Mon, 13 Feb 2017 12:30:29 -0800, Gerald Burns wrote:
> Excuse me for being a total noob, but I'm unsure of how to reply to a
> mailing list.
Just Reply to List if your email client offers that, otherwise use Reply
and specify the list email address as in your original post.
> Regarding xtail being the same as fswatch, I believe they are
> different. It sounds like xtail lets you physically see changes with
> your eyeballs, where as fswatch is the watcher and can notify other
> programs when changes occur.
Gives you the name and content so you have more info to decide what you
want to do.
> In my particular scenario we have written a little script that uses
> fswatch to monitor a directory, and when any changes occur they are
> rsync'd to a remote server.
For that use case, fswatch may be a better choice.
You could just run an rsync command regularly in a cron job.
> Thanks, and sorry again if this is bad etiquette.
> https://cygwin.com/ml/cygwin/2017-02/msg00171.html
Breaks proper thread message header references.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next parent reply other threads:[~2017-02-14 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAABYpSiQVASBNiEUsJYgMx3WsYTDxYhbKi-XpjpFzU9qFVMEwg@mail.gmail.com>
2017-02-14 2:47 ` Brian Inglis [this message]
2017-02-13 9:11 Gerald Burns
2017-02-13 15:03 ` Andrew Schulman
2017-02-13 17:05 ` Brian Inglis
2017-02-14 8:55 ` Vlado
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4925792d-5253-b159-aff1-8b15bdeb4432@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).