Kevin McAllister on 12 Jan 2013 06:20:55 -0800

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] General "incoming" file processor or framework?

We needed something like that at work and ended up writing our own thing, really a simple bash script with some locking. And we didn't bother with inotify because every-few-minute checks achievable by cron was good enough for our application.

Though if you search for content-distribution there may be a general solution inside some CDN system you can extract. We didn't go too far in those searches because the rapid prototype was deemed good enough to be hardened for production.

Let us know if you find anything interesting.

On Jan 12, 2013, at 1:02 AM, JP Vossen <> wrote:

> Is anyone aware of any kind of general "incoming" file processor or framework?  I'm not talking about 'inotify' but something more like:
> 1) Notice an arbitrary file has appeared in an arbitrary location
>    1.1) Maybe by using inotify, but that's not the point
> 2) Perform some arbitrary action on the file based on arbitrary rules
> One use-case would be for "write only" storage for log or audit data for PCI compliance.  So you transmit the data as a tarball into some writeable directory via scp or whatever, and the file is picked up, hashed, manifested, processed or just moved to a read-only archive location from which it may be later downloaded if needed.
> It's not all that hard to do, but it seems like a reasonably obvious task that may already exist, but if so I'm not finding it.  Years ago I might have looked for something called a "drop box" but these days that term is swamped into uselessness...
> I would need something small and stand-alone, something built into a giant framework like Rails or Zope is unnecessary overkill.
> Clues?  Thanks,
> JP
> ----------------------------|:::======|-------------------------------
> JP Vossen, CISSP            |:::======|
> My Account, My Opinions     |=========|
> ----------------------------|=========|-------------------------------
> "Microsoft Tax" = the additional hardware & yearly fees for the add-on
> software required to protect Windows from its own poorly designed and
> implemented self, while the overhead incidentally flattens Moore's Law.
> ___________________________________________________________________________
> Philadelphia Linux Users Group         --
> Announcements -
> General Discussion  --
Philadelphia Linux Users Group         --
Announcements -
General Discussion  --