Yes, that's why it is so strange that it was not enough to stop Kannel from
sending messages.
That's also in his email.

Hence, my question to Ulf: What do you mean exactly?

== Rene

-----Original Message-----
From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: donderdag 15 juli 2010 16:37
To: Rene Kluwen; 'Ulf Urden'; users@kannel.org
Subject: Re: Kannel store/queue

You disappoint me, Rene. Reread his mail more carefully. He is very 
explicit:

>>> There are no stores in my /etc/kannel/kannel.conf
>>>
>>> Neither store-type nor store-location is defined in it.

Nikos
----- Original Message ----- 
From: "Rene Kluwen" <rene.klu...@chimit.nl>
To: "'Nikos Balkanas'" <nbalka...@gmail.com>; "'Ulf Urden'" 
<ulf.ur...@purplescout.se>; <users@kannel.org>
Sent: Thursday, July 15, 2010 4:19 PM
Subject: RE: Kannel store/queue


> He says:
>
>>> I need to make sure Kannel has no queue or pending messages when I start
>>> the daemon. How can I do that?
>
> So to my understanding he wants to purge the queue before starting Kannel.
>
> Ulf: Can you clarify your question?
>
> == Rene
>
> -----Original Message-----
> From: Nikos Balkanas [mailto:nbalka...@gmail.com]
> Sent: donderdag 15 juli 2010 15:13
> To: Rene Kluwen; 'Ulf Urden'; users@kannel.org
> Subject: Re: Kannel store/queue
>
> Rene,
>
> To my understanding Ulf just wants a quick, clean shutdown. He thinks that
> queue is his problem, but I don't think so with the traffic he has, so
> that's why I am asking for his logs...
>
> BR,
> Nikos
>
> ----- Original Message ----- 
> From: "Rene Kluwen" <rene.klu...@chimit.nl>
> To: "'Nikos Balkanas'" <nbalka...@gmail.com>; "'Ulf Urden'"
> <ulf.ur...@purplescout.se>; <users@kannel.org>
> Sent: Thursday, July 15, 2010 3:58 PM
> Subject: RE: Kannel store/queue
>
>
>>I think that Ulf wants to have NO queue. Instead of a spool queue.
>>
>> == Rene
>>
>> -----Original Message-----
>> From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On 
>> Behalf
>> Of Nikos Balkanas
>> Sent: donderdag 15 juli 2010 11:42
>> To: Ulf Urden; users@kannel.org
>> Subject: Re: Kannel store/queue
>>
>> Hi,
>>
>> Simple answer. You can't. SMS is asynchronous, therefore multiple queues
>> have been implemented. Even if you don't have a file queue, Kannel still
>> has
>>
>> a lot of memory queues. By typeing <Ctrl-C> twice, kannel will die
>> immediately, but you will loose all pending SMS in memory.
>>
>> You should have a file storage. In fact having all sms in memory is
>> causing
>> kannel to delay, since it tries to process these SMS before quitting. 
>> File
>> storage doesn't affect that behaviour, and on top of that will preserve
>> SMS
>> if you try a double <Ctrl-C>.
>>
>> Configure store-type as spool. If you still get problems shutting down,
>> please post maximum detail bb logs of your shutdown attempt.
>>
>> BR,
>> Nikos
>> ----- Original Message ----- 
>> From: "Ulf Urden" <ulf.ur...@purplescout.se>
>> To: <users@kannel.org>
>> Sent: Thursday, July 15, 2010 11:47 AM
>> Subject: Kannel store/queue
>>
>>
>>> Hi!
>>>
>>> I'm trying to find out the default behavior of Kannel when no store or
>>> spool is defined.
>>>
>>> I have a system that, using HTTP requests to Kannel, send SMS's to end
>>> users. The typical usage is around a few hundred SMS's per day. Because
>>> my
>>
>>> system is now about to be upgraded, I shut down the daemon that sends 
>>> the
>>> requests to Kannel, but unfortunately that was not enough to stop 
>>> sending
>>> SMS's because Kannel seemed to throttle and queue the requests, 
>>> spreading
>>> out messages 24hrs after that until I shut down /etc/init.d/kannel.
>>>
>>> There are no stores in my /etc/kannel/kannel.conf
>>>
>>> Neither store-type nor store-location is defined in it. Will Kannel keep
>>> a
>>
>>> persistent disk queue somewhere anyway?
>>>
>>> I need to make sure Kannel has no queue or pending messages when I start
>>> the daemon. How can I do that?
>>>
>>> I'm using 1.4.1-2, Debian Lenny.
>>>
>>> BR,
>>> Ulf
>>>
>>> Software Engineer
>>> Purple Scout
>>> www.purplescout.com
>>>
>>
>>
>>
>>
>
>
> 




Reply via email to