> From: Nico Kadel-Garcia [mailto:nka...@gmail.com]
> On Mon, Nov 22, 2010 at 9:55 PM, Andrey Repin
> > Cron job won't be able to know if file transfer is completed. It
> > will have to guess from, e.g., testing the archive (if it's
> > archive) for integrity. filesystem notification mechanism w
On Mon, Nov 22, 2010 at 9:55 PM, Andrey Repin wrote:
> Greetings, Les Mikesell!
>
>> Realistically, you probably don't need to kick off the job the instant
>> the filesystem changes - you'll at least want to wait until the file
>> transfer completes. I'd expect a scheduled job running from cron o
On 11/22/10 8:55 PM, Andrey Repin wrote:
Greetings, Les Mikesell!
Realistically, you probably don't need to kick off the job the instant
the filesystem changes - you'll at least want to wait until the file
transfer completes. I'd expect a scheduled job running from cron on
linux or the windows
Greetings, Les Mikesell!
> Realistically, you probably don't need to kick off the job the instant
> the filesystem changes - you'll at least want to wait until the file
> transfer completes. I'd expect a scheduled job running from cron on
> linux or the windows task scheduler checking for new f
On 11/22/2010 12:14 PM, David Weintraub wrote:
On Mon, Nov 22, 2010 at 12:50 PM, Les Mikesell wrote:
I'm not that familiar with AIX, but linux has per-user crontabs so if you
have a login and access to the files under that login you would
automatically have "scheduling abilities". I thought th
On Mon, Nov 22, 2010 at 12:50 PM, Les Mikesell wrote:
> I'm not that familiar with AIX, but linux has per-user crontabs so if you
> have a login and access to the files under that login you would
> automatically have "scheduling abilities". I thought that was true for most
> things based on SysV'
On 11/22/2010 11:24 AM, David Weintraub wrote:
Well, the file system triggers are nice to know, but I'm too low level
a peon in order to implement such a policy on our servers. Besides, we
use AIX and not Linux here.
So I have the following choices:
* Use a crontab entry to look for changes eve
Well, the file system triggers are nice to know, but I'm too low level
a peon in order to implement such a policy on our servers. Besides, we
use AIX and not Linux here.
So I have the following choices:
* Use a crontab entry to look for changes every five minutes or so.
* Use Hudson and use its F
On 11/22/2010 10:44 AM, Andy Levy wrote:
On Mon, Nov 22, 2010 at 11:36, Ludwig, Michael
wrote:
From: Andrey Repin
Sent: Monday, November 22, 2010 5:11 PM
Any ideas of any software that can handle this.
You'd be surprised, but the very filesystem (in Unix/Linux at
least) support
trigger me
On Mon, Nov 22, 2010 at 11:36, Ludwig, Michael
wrote:
>> From: Andrey Repin
>> Sent: Monday, November 22, 2010 5:11 PM
>
>> > Any ideas of any software that can handle this.
>>
>> You'd be surprised, but the very filesystem (in Unix/Linux at
>> least) support
>> trigger mechanism. All you need is
> From: Andrey Repin
> Sent: Monday, November 22, 2010 5:11 PM
> > Any ideas of any software that can handle this.
>
> You'd be surprised, but the very filesystem (in Unix/Linux at
> least) support
> trigger mechanism. All you need is to write appropriate filter.
I think one such mechanism for
Greetings, David Weintraub!
> Any ideas of any software that can handle this.
You'd be surprised, but the very filesystem (in Unix/Linux at least) support
trigger mechanism. All you need is to write appropriate filter.
--
WBR,
Andrey Repin (anrdae...@freemail.ru) 22.11.2010, <19:09>
Sorry for
12 matches
Mail list logo
