On Thu, Jun 26, 2008 at 8:44 PM, Michael Stone <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 26, 2008 at 07:10:18PM -0400, [EMAIL PROTECTED] wrote:
> Are we content with the exceptions that might result from
> postprocessing.py if run with fewer than two arguments? Do we ever
> expect that postprocess.p
On Thu, Jun 26, 2008 at 07:10:18PM -0400, [EMAIL PROTECTED] wrote:
> diff --git a/server/postprocess.py b/server/postprocess.py
> new file mode 100755
> index 000..82a2418
> --- /dev/null
> +++ b/server/postprocess.py
> +homebasepath = '/library/users'
> +dirpath = sys.argv[1]
> +fname
From: Martin Langhoff <[EMAIL PROTECTED]>
After a complete rsync transfer, clients will touch a file in
a "trigger" directory. incrond will call postprocess.py to
perform any actions required. With this commit we have
- a paranoid initial part of postprocess, that performs
sanity checks and t
