On Wed, 2008-09-03 at 00:55 -0500, Micah Gersten wrote:
> Robert Cummings wrote:
> > On Mon, 2008-09-01 at 14:34 +0200, Merlin Morgenstern wrote:
> >
> >> Per Jessen schrieb:
> >>
> >>> Jochem Maas wrote:
> >>>
> >>>
> > lockfile=/var/lock//file
> > # clear out a lock older t
Robert Cummings wrote:
> On Mon, 2008-09-01 at 14:34 +0200, Merlin Morgenstern wrote:
>
>> Per Jessen schrieb:
>>
>>> Jochem Maas wrote:
>>>
>>>
> lockfile=/var/lock//file
> # clear out a lock older than 60mins
> find $lockfile -cmin +60 | xargs rm
> test ! -f $lockf
Robert Cummings schreef:
On Mon, 2008-09-01 at 14:34 +0200, Merlin Morgenstern wrote:
Per Jessen schrieb:
Jochem Maas wrote:
lockfile=/var/lock//file
# clear out a lock older than 60mins
find $lockfile -cmin +60 | xargs rm
test ! -f $lockfile && (
touch $lockfile
rm -f $lockfile
)
wouldn't
On Mon, 2008-09-01 at 14:34 +0200, Merlin Morgenstern wrote:
> Per Jessen schrieb:
> > Jochem Maas wrote:
> >
> >>> lockfile=/var/lock//file
> >>> # clear out a lock older than 60mins
> >>> find $lockfile -cmin +60 | xargs rm
> >>> test ! -f $lockfile && (
> >>> touch $lockfile
> >>>
> >>> rm -f
Per Jessen schrieb:
Jochem Maas wrote:
lockfile=/var/lock//file
# clear out a lock older than 60mins
find $lockfile -cmin +60 | xargs rm
test ! -f $lockfile && (
touch $lockfile
rm -f $lockfile
)
wouldn't creating a dir be better here? (with regard to atomicity)
I haven't thought it throug
Robert Cummings schreef:
On Sun, 2008-08-31 at 16:25 -0400, Robert Cummings wrote:
On Sun, 2008-08-31 at 22:21 +0200, Jochem Maas wrote:
Robert Cummings schreef:
On Sun, 2008-08-31 at 21:42 +0200, Jochem Maas wrote:
Robert Cummings schreef:
I assume that this is coming from your inter
On Sun, 2008-08-31 at 16:25 -0400, Robert Cummings wrote:
> On Sun, 2008-08-31 at 22:21 +0200, Jochem Maas wrote:
> > Robert Cummings schreef:
> > > On Sun, 2008-08-31 at 21:42 +0200, Jochem Maas wrote:
> > >> Robert Cummings schreef:
> >
> >
> >
> > >> I assume that this is coming from your
On Sun, 2008-08-31 at 22:21 +0200, Jochem Maas wrote:
> Robert Cummings schreef:
> > On Sun, 2008-08-31 at 21:42 +0200, Jochem Maas wrote:
> >> Robert Cummings schreef:
>
>
>
> >> I assume that this is coming from your interjinn lib, and that it's
> >> aimed at php4 (given the ampersands you
Robert Cummings schreef:
On Sun, 2008-08-31 at 21:42 +0200, Jochem Maas wrote:
Robert Cummings schreef:
I assume that this is coming from your interjinn lib, and that it's
aimed at php4 (given the ampersands your throwing about)
also your LockManager object seems to have a get() and ge
On Sun, 2008-08-31 at 21:42 +0200, Jochem Maas wrote:
> Robert Cummings schreef:
> > On Sun, 2008-08-31 at 17:10 +0200, Jochem Maas wrote:
> >> Robert Cummings schreef:
> >>> On Sun, 2008-08-31 at 12:12 +0200, Per Jessen wrote:
> Robert Cummings wrote:
>
> >> That's easily taken care
Robert Cummings schreef:
On Sun, 2008-08-31 at 17:10 +0200, Jochem Maas wrote:
Robert Cummings schreef:
On Sun, 2008-08-31 at 12:12 +0200, Per Jessen wrote:
Robert Cummings wrote:
That's easily taken care of. Instead of a cron-job, you could have a
script running as a daemon, checking for e
On Sun, 2008-08-31 at 17:10 +0200, Jochem Maas wrote:
> Robert Cummings schreef:
> > On Sun, 2008-08-31 at 12:12 +0200, Per Jessen wrote:
> >> Robert Cummings wrote:
> >>
> That's easily taken care of. Instead of a cron-job, you could have a
> script running as a daemon, checking for ema
Robert Cummings schreef:
On Sun, 2008-08-31 at 12:12 +0200, Per Jessen wrote:
Robert Cummings wrote:
That's easily taken care of. Instead of a cron-job, you could have a
script running as a daemon, checking for emails to be sent every
5mins.
That's the same as running a cron every 5 minutes
On Sun, 2008-08-31 at 12:49 +0200, Per Jessen wrote:
> Robert Cummings wrote:
>
> > On Sun, 2008-08-31 at 12:12 +0200, Per Jessen wrote:
> >> Robert Cummings wrote:
> >>
> >> >> That's easily taken care of. Instead of a cron-job, you could
> >> >> have a script running as a daemon, checking for
Robert Cummings wrote:
> On Sun, 2008-08-31 at 12:12 +0200, Per Jessen wrote:
>> Robert Cummings wrote:
>>
>> >> That's easily taken care of. Instead of a cron-job, you could
>> >> have a script running as a daemon, checking for emails to be sent
>> >> every 5mins.
>> >
>> > That's the same as
On Sun, 2008-08-31 at 12:12 +0200, Per Jessen wrote:
> Robert Cummings wrote:
>
> >> That's easily taken care of. Instead of a cron-job, you could have a
> >> script running as a daemon, checking for emails to be sent every
> >> 5mins.
> >
> > That's the same as running a cron every 5 minutes ex
Robert Cummings wrote:
>> That's easily taken care of. Instead of a cron-job, you could have a
>> script running as a daemon, checking for emails to be sent every
>> 5mins.
>
> That's the same as running a cron every 5 minutes except now you also
> need to detect if your daemon dies :) On the pl
On Sat, 2008-08-30 at 22:14 +0200, Per Jessen wrote:
> Merlin wrote:
>
> > I am thinking about placing the info on the individual e-mail inside a
> > ascii txt file that will be read by a cron job which will send the
> > e-mail instead. Something like every 5 minutes reading it line by line
> > an
Well, i have done that once and it worked pretty well...
Only diference was that i had a hour limit ( think dreamhost hosting )
and used Swift Mailer, but i think it don't matter a lot ;)
I think is a good solution...
On Sat, Aug 30, 2008 at 6:40 PM, Merlin <[EMAIL PROTECTED]> wrote:
> Hi everybod
Merlin wrote:
> I am thinking about placing the info on the individual e-mail inside a
> ascii txt file that will be read by a cron job which will send the
> e-mail instead. Something like every 5 minutes reading it line by line
> and then after sending it removing the line.
> e.g:
> for:[EMAIL PR
Hi everybody,
I am running a travel community where users want to get informed on
changes inside different groups they have subscribed to.
At the moment I am doing this with a for loop that generates an
individual e-mail sent to them via phpmailer. That works, however the
submit of the conte
21 matches
Mail list logo
